From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 128798 invoked by alias); 10 Dec 2018 13:54:25 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 128779 invoked by uid 89); 10 Dec 2018 13:54:24 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=2.3 required=5.0 tests=BAYES_50,HTML_MESSAGE,KAM_LAZY_DOMAIN_SECURITY,KAM_NUMSUBJECT,RCVD_IN_DNSWL_NONE autolearn=no version=3.3.2 spammy=announcement, cmd, p.s, capable X-HELO: mout.kundenserver.de Received: from mout.kundenserver.de (HELO mout.kundenserver.de) (212.227.126.131) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Mon, 10 Dec 2018 13:54:22 +0000 Received: from [10.161.52.42] ([178.19.220.109]) by mrelayeu.kundenserver.de (mreue012 [212.227.15.167]) with ESMTPSA (Nemesis) id 1MnFps-1hDMLP0hvg-00jJVO for ; Mon, 10 Dec 2018 14:54:19 +0100 Subject: Re: [ANNOUNCEMENT] Updated: mintty 2.9.5 To: cygwin@cygwin.com References: <87woon9133.fsf@Rainer.invalid> <87in06la12.fsf@Rainer.invalid> <94206790.20181207003223@yandex.ru> <2f3cf57e-0b44-8c4a-b075-24743e4443d2@towo.net> <199122924.20181208004157@yandex.ru> <482194f6-37e5-6892-f63f-d7474cdab694@towo.net> <753995611.20181210050159@yandex.ru> <1277174748.20181210160853@yandex.ru> From: Thomas Wolff Message-ID: Date: Mon, 10 Dec 2018 13:54:00 -0000 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: <1277174748.20181210160853@yandex.ru> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2018-12/txt/msg00094.txt.bz2 Hello Andrey, On 10.12.2018 14:08, Andrey Repin wrote: > Greetings, Thomas Wolff! > >>>>> BTW, Cygwin itself does it differently. %Cygwin%\bin is converted to /usr/bin. >>>> This setup should be handled in the Posix path domain. >>> Give me a good reason why should you second-guess Cygwin's own functionality? >> You have apparently set up some cmd scripts as mintty user commands, so >> you're thinking in Windows terms here. > One is very distantly related to another. > I set up programs to work as user commands, it's not actually relevant, if > they are cmd scripts, or perl, both, or neither. Acknowledged. >> However, the idea is more to use cygwin tools for such purposes. In either >> case, the path is handled within a cygwin session (mintty) and cygwin does >> the conversion both ways, so it should be fine for you. > The path is handled within a **cygwin** session, but mintty is not it. Sure mintty is a cygwin program, linked with cygwin and thus starting a cygwin session. > And you don't have to second-guess cygwin behavior, if you do it the way I > propose. And you would be safe if behavior would one day change (though I do > not foresee it in this case). I'm not tampering with cygwin behaviour in any way, just changing PATH, so that a tool subsequently invoked by `popen` can use it. > P.S. > I've tried to do it "your way" for tests. > Had enough of an issue starting Cygwin itself and rolled it back. > Cygwin already quite capable of path conversion, no need to deny it this ability. Not sure whether you're having a problem with your mintty command scripts. I've tested this thoroughly, everything works fine in these configuration combinations, with a test script D:\bin\test.cmd that echoes %MINTTY_SELECT% attached to keyboard shortcut Ctrl+Shift+t: KeyFunctions=t:`test.cmd` UserCommandsPath=D:\bin:%s KeyFunctions=t:`test.cmd` UserCommandsPath=/cygdrive/d/bin:%s KeyFunctions=t:`D:/bin/test.cmd` #UserCommandsPath= KeyFunctions=t:`/cygdrive/d/bin/test.cmd` #UserCommandsPath= -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple