From: Thomas Wolff <towo@towo.net>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Updated: mintty 2.9.5
Date: Mon, 10 Dec 2018 04:58:00 -0000 [thread overview]
Message-ID: <fa4263d7-9e16-42d0-be7d-8ef88dde5cff@towo.net> (raw)
In-Reply-To: <753995611.20181210050159@yandex.ru>
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
next prev parent reply other threads:[~2018-12-10 4:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-05 10:28 Thomas Wolff
2018-12-05 20:21 ` Achim Gratz
2018-12-05 21:46 ` Thomas Wolff
2018-12-06 0:20 ` Andrey Repin
2018-12-06 7:22 ` Thomas Wolff
2018-12-06 16:25 ` cyg Simple
2018-12-06 19:39 ` Achim Gratz
2018-12-06 21:35 ` Andrey Repin
2018-12-07 20:12 ` Thomas Wolff
2018-12-07 21:50 ` Andrey Repin
2018-12-09 23:22 ` Thomas Wolff
2018-12-10 2:05 ` Andrey Repin
2018-12-10 4:58 ` Thomas Wolff [this message]
2018-12-10 13:20 ` Andrey Repin
2018-12-10 13:54 ` Thomas Wolff
2018-12-07 13:45 ` Brian Inglis
2018-12-10 18:21 ` Achim Gratz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fa4263d7-9e16-42d0-be7d-8ef88dde5cff@towo.net \
--to=towo@towo.net \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).