public inbox for
 help / color / mirror / Atom feed
From: Andrey Repin <>
To: Achim Gratz <>,
Subject: Re: How to handle length limit of PATH environment variable
Date: Fri, 06 Apr 2018 00:35:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <87o9ixfq21.fsf@Rainer.invalid>

Greetings, Achim Gratz!

> Andrey Repin writes:
>> P.P.S.
>> Partial solution could be a wrapper that reduce PATH length by dropping
>> nonessential/duplicate/Win-specific paths before invoking Cygwin terminal.
>> I have such a wrapper for my own reasons.

> You don't need one if your login shell is a POSIX shell and you don't
> use Windows applications if you have set a system or user variable
> CYGWIN_NOWINPATH to a non-empty value.

What if I explicitly do not want to do that?
It reduces interoperability to miniscule levels.

> It's usually way easier to add to a clean path than removing cruft and I
> generally lean into the direction of using wrapper scripts for Windows
> applications that I need to use from Cygwin since quite often some other
> things need attention aside from PATH.

For me, it's easier to wrap Cygwin apps, since I have sane wrapping material
(and many Cygwin tools not requiring any wrapping to begin with).

With best regards,
Andrey Repin
Friday, April 6, 2018 03:18:18

Sorry for my terrible english...

Problem reports:
Unsubscribe info:

  reply	other threads:[~2018-04-06  0:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-05  9:19 Peter Bauer
2018-04-05 10:06 ` Wolf Geldmacher
2018-04-05 16:26   ` Brian Inglis
2018-04-05 11:50 ` Steven Penny
2018-04-05 17:50 ` Andrey Repin
2018-04-05 18:48   ` Achim Gratz
2018-04-06  0:35     ` Andrey Repin [this message]
2018-04-11 13:43     ` Peter Bauer
2018-04-06  0:31 ` Hans-Bernhard Bröker

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

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