DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:subject:reply-to:to:references:message-id
	:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=mdcas0qCuQKTNk6k
	CybwXhJywgx2GHZEjOlRwzOKNUeC4f4+WIysWvwBQgu1SPPmT15e9M35jIP1f33+
	+znJjPVfNL1xx7AecesyvCeNyZjk/CSbQNECgrg68J33AcEzO+HgjVP3K5E9BHSB
	msm3HuzuObw7AuKMd6jDrDKcLTI=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
Subject: [ANNOUNCEMENT] Updated: mintty 2.9.5
Reply-To: Brian.Inglis@SystematicSw.ab.ca
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>
Openpgp: preference=signencrypt
Message-ID: <890e52de-5115-0021-57ef-3178053e9328@SystematicSw.ab.ca>
Date: Fri, 7 Dec 2018 06:45:51 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.3.2
MIME-Version: 1.0
In-Reply-To: <87in06la12.fsf@Rainer.invalid>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

On 2018-12-06 12:39, Achim Gratz wrote:
> Thomas Wolff writes:
>> Am 05.12.2018 um 21:21 schrieb Achim Gratz:
>>> Thomas Wolff writes:
>>>> Ensuring /bin in PATH for user commands.
>>> Blindly prepending /bin to the existing PATH is asking for trouble with 
>>> certain setups.

Many setups: my Windows User PATH includes Cygwin {,/usr/local}/{,s}bin and the
Windows System PATH, and my login scripts append new Cygwin paths before any
Windows paths, used to allow interop using Cygwin and Windows consoles with
Cygwin and non-Cygwin apps, which may only or also be available in MinGW/native
exes e.g. BitKeeper.

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

after checking to see if the expected /bin is already present

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

Maybe allow an env config file with comments, blank lines, env var definitions
with values including embedded single and double quotes, env var refs, and one
optional prefix command e.g. export, set, setenv, etc. which could be ignored
when used without a definition e.g. "export PATH" rather than "export PATH=...".

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.

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