From: J M <cesarjorgemartinez@gmail.com>
To: cygwin@cygwin.com
Subject: Re: See repeated /usr/bin in my path
Date: Wed, 17 Apr 2024 23:43:43 +0200 [thread overview]
Message-ID: <CAL8MddVrZqq6O9=jCP39Aht5qV_T11tbFSMr0Y5qUJUjYa7Xjg@mail.gmail.com> (raw)
In-Reply-To: <297943415.20240418002244@yandex.ru>
[-- Attachment #1: Type: text/plain, Size: 1269 bytes --]
Hi Andrew,
Isn't it better that original_path be removed all startwith
$mycygwin_homepath?
You have this scriptlet, but if you need all to work with all Linux
distributions you need yo add unnecessary work, multiple code and cases for
all, and complicate all.
Regards
El mié., 17 abr. 2024 23:35, Andrey Repin <anrdaemon@yandex.ru> escribió:
> Greetings, J M!
>
> > I think that is a bug, in my Windows environment path I have this:
> > C:\cygwin64\bin
>
> > Then for some mystery change this to /usr/bin, instead to delete.
> > You can file an issue?
>
> It's not a bug, it's how Cygwin works.
> If you want to have Cygwin in your system PATH, you'll have to, either
> a) tolerate the duplicated entries in session's $PATH, or
> b) do something to fix it.
>
> I use this scriptlet:
>
> PATH="$( tr ":" "\\n"
> <<<"$HOME/bin:$HOME/.local/bin:/usr/local/bin:/bin:$PATH" | sed -Ee "1,4b;
> \\#Subversion|$HOME|^(/usr(/local)?)?/bin\$#d;" | paste -sd:)" export PATH
>
> (Essentially, I push 4 predefined paths on top of the stack, then filter
> out
> the rest of the stack by some known patterns.)
>
>
> --
> With best regards,
> Andrey Repin
> Thursday, April 18, 2024 00:07:59
>
> Sorry for my terrible english...
>
>
next prev parent reply other threads:[~2024-04-17 21:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-17 17:10 J M
2024-04-17 17:29 ` J M
2024-04-17 21:22 ` Andrey Repin
2024-04-17 21:43 ` J M [this message]
2024-04-18 16:41 ` Andrey Repin
2024-04-18 16:59 ` Eliot Moss
2024-04-19 14:45 ` J M
2024-04-17 20:58 ` Doug Henderson
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='CAL8MddVrZqq6O9=jCP39Aht5qV_T11tbFSMr0Y5qUJUjYa7Xjg@mail.gmail.com' \
--to=cesarjorgemartinez@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).