From: Peter Bauer <peter.m.bauer@gmail.com>
To: cygwin@cygwin.com
Subject: Re: How to handle length limit of PATH environment variable
Date: Wed, 11 Apr 2018 13:43:00 -0000 [thread overview]
Message-ID: <e30bb5c7-b61c-9465-0407-3c3f2af57d8b@gmail.com> (raw)
In-Reply-To: <87o9ixfq21.fsf@Rainer.invalid>
On 04/05/2018 08:47 PM, Achim Gratz wrote:
> 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. For tcsh I have patched
> /etc/csh.login to do the moral equivalent; I guess that should be
> packaged with tcsh eventually.
>
> 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.
>
i went for this solution as the default PATH after opening a Cygwin
terminal was already ~2000 characters long.
thx a lot,
Peter
--
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-04-11 13:43 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
2018-04-11 13:43 ` Peter Bauer [this message]
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:
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=e30bb5c7-b61c-9465-0407-3c3f2af57d8b@gmail.com \
--to=peter.m.bauer@gmail.com \
--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).