From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Updated: mintty 2.9.5
Date: Thu, 06 Dec 2018 19:39:00 -0000 [thread overview]
Message-ID: <87in06la12.fsf@Rainer.invalid> (raw)
In-Reply-To: <a753939f-9724-296a-8ec5-643cd09b4f93@towo.net> (Thomas Wolff's message of "Wed, 5 Dec 2018 22:46:05 +0100")
Thomas Wolff writes:
> Am 05.12.2018 um 21:21 schrieb Achim Gratz:
>> Thomas Wolff writes:
>>> Other
>>> * Ensuring /bin in PATH for user commands.
>> Blindly prepending /bin to the existing PATH is asking for trouble with certain setups.
> Just to clarify, this is only applicable to user-defined commands
> added to the extended context menu (option UserCommands), in order to
> ensure basic tools are available. If you see problems there, please be
> more specific.
I'm not using this option, so my remark was just to remind you that
second-guessing the user w.r.t. PATH will eventually find at least one
user in an unfortunate (and in this case hard to debug) situation. So
the usual advice applies:
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.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
SD adaptations for KORG EX-800 and Poly-800MkII V0.9:
http://Synth.Stromeko.net/Downloads.html#KorgSDada
--
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-06 19:39 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 [this message]
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
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=87in06la12.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--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).