DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=pnQclgzUF5/qNvgk
	UsySw+4TawZvdn0I0riIaCB0v0vTlV24jLTkZj6u62pHo8lL6W0QytJASp7sUJg4
	U9fE5NFuq9d3G9yaIdD0LqiMOo5ZxmBMf42yZqyubVfAv0h3Qhc/rpBl7PxeRo4r
	Szu39Q2Ow4my44WC2dNmd69Oq2s=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Updated: mintty 2.9.5
To: cygwin@cygwin.com
References: <announce.ba14b773-7e0a-32fd-7a01-4979c60eeb4c@towo.net> <87woon9133.fsf@Rainer.invalid> <a753939f-9724-296a-8ec5-643cd09b4f93@towo.net> <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> <fa4263d7-9e16-42d0-be7d-8ef88dde5cff@towo.net> <1277174748.20181210160853@yandex.ru>
From: Thomas Wolff <towo@towo.net>
Message-ID: <b11ce6c0-333c-045b-74f8-d4d27be6f8da@towo.net>
Date: Mon, 10 Dec 2018 14:54:17 +0100
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

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