From: Andrey Repin <anrdaemon@yandex.ru>
To: tealhill <tealhill@gmail.com>, cygwin@cygwin.com
Subject: Re: Please add /cygdrive/c/Windows/Sysnative to the default PATH
Date: Thu, 19 Nov 2020 12:15:56 +0300 [thread overview]
Message-ID: <1048421804.20201119121556@yandex.ru> (raw)
In-Reply-To: <rp1n3r$2ut$1@ciao.gmane.io>
Greetings, tealhill!
> On 2020-11-17 4:23 PM, Thomas Wolff wrote:
>> Am 17.11.2020 um 20:54 schrieb tealhill via Cygwin:
>>>
>>> Cygwin's /etc/profile sets the PATH.
>>>
>>> Could /etc/profile please also add /cygdrive/c/Windows/Sysnative to
>>> the end of the PATH?
>>
>> It doesn't add any other Windows folders so why this one.
> ### Summary
> Why should Cygwin add Sysnative to $PATH? As a workaround for
> Microsoft's failure to add Sysnative to %PATH%.
It was never a failure.
And if you use proper platform tools, it's not an issue either.
> ### Full explanation
> Cygwin imports the Windows %PATH% variable at startup.
Not necessarily. Depends on your .profile configuration.
> It would be ideal if Microsoft would add Sysnative to the default
> Windows %PATH%.
No, that would be a disaster.
> Such a change would help Cygwin users and others. But
> I doubt that Microsoft will make this change.
> Therefore, I am suggesting that Cygwin work around Microsoft's omission.
> My suggested workaround is for Cygwin to add Sysnative to its own
> $PATH, automatically.
I'm suggesting you install 64-bit Cygwin already.
32-bit Cygwin is rapidly running out of its usefulness.
--
With best regards,
Andrey Repin
Thursday, November 19, 2020 12:13:58
Sorry for my terrible english...
next prev parent reply other threads:[~2020-11-19 9:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-17 19:54 tealhill
2020-11-17 21:23 ` Thomas Wolff
2020-11-17 23:41 ` tealhill
2020-11-18 15:21 ` Bill Stewart
2020-11-18 15:45 ` Achim Gratz
2020-11-19 9:15 ` Andrey Repin [this message]
2020-11-19 15:57 ` Brian Inglis
2020-11-24 7:24 ` Thomas Wolff
2020-11-24 14:52 ` Bill Stewart
2020-11-24 15:10 ` Hamish McIntyre-Bhatty
2020-11-24 21:06 ` Brian Inglis
2020-11-24 1:58 ` L A Walsh
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=1048421804.20201119121556@yandex.ru \
--to=anrdaemon@yandex.ru \
--cc=cygwin@cygwin.com \
--cc=tealhill@gmail.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).