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=G/pTNck5wqgnxKSS
	nhNWBKfTXAM/QMq+n1vTYaKhXK63YiP5xmy40mAkR6sQ4cRIdYHNOVUCfLvASND2
	FlAmdztPhtpaylhDFC734fPaSRQGkF53S1Op6K6vLEUjWNV9bE+i3osS/03WsiYL
	u021zUXvmdngpyNnPTeNHni6bdE=
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>
From: Thomas Wolff <towo@towo.net>
Message-ID: <fa4263d7-9e16-42d0-be7d-8ef88dde5cff@towo.net>
Date: Mon, 10 Dec 2018 05:58:17 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.3.3
MIME-Version: 1.0
In-Reply-To: <753995611.20181210050159@yandex.ru>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

Am 10.12.2018 um 03:01 schrieb Andrey Repin:
> Greetings, Thomas Wolff!
>
>> Am 07.12.2018 um 22:41 schrieb Andrey Repin:
>>> Greetings, Thomas Wolff!
>>>
>>>> Am 06.12.2018 um 22:32 schrieb Andrey Repin:
>>>>> Greetings, Achim Gratz!
>>>>>
>>>>>> a) Just warn about the missing PATH component without changing the PATH.
>>>>>> b) Give the user an option to let the command run with a separate PATH.
>>>>>> Indeed there might be other things that are missing in the environment,
>>>>>> so instead of just fixing up PATH you might consider using a wrapper
>>>>>> that the user can change.
>>>>> This is an interesting point.
>>>>> Probably letting the user specify custom $PATH for quick commands (and save
>>>>> current %PATH% as $ORIGINAL_PATH) may be the best choice.
>>>>> The default can be %Cygwin%\bin:%PATH% or %PATH%:%Cygwin%\bin, I'm not very
>>>>> concerned as long as it's explicit and customizable.
>>>> I didn't expect the setup of this specific feature to be so strongly
>>>> advocated :)
>>>> In any case, things shouldn't become too complex. What I can image is an
>>>> option UserCommandsPATH
>>>> with one optional placeholder %s which would be replaced with the
>>>> environment PATH;
>>>> default /bin:%s, corresponding to current behaviour.
>>> Using native paths and environment variable syntax, you can always use
>>> ExpandEnvironmentString to get the %PATH% you need.
>>> Cygwin DLL will then convert it to own version, avoiding you mangling it
>>> yourself.
>>> And I would strongly discourage from using placeholders familiar for you, but
>>> unexpected by the end user and taken from entirely different area of knowledge.
>>>
>>> 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. 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.
Thomas

>
>> I've uploaded a
>> patch for evaluation, to the github repository.
>> Thomas

--
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