From: Dave Kilroy <kilroyd@googlemail.com>
To: cygwin@cygwin.com
Subject: Re: fish PATH problem
Date: Thu, 09 Oct 2014 21:55:00 -0000 [thread overview]
Message-ID: <54370457.8060905@gmail.com> (raw)
In-Reply-To: <1938036834.20141009212648@yandex.ru>
On 09/10/2014 18:26, Andrey Repin wrote:
> Greetings, Andrew Schulman!
>
>> Bad news: the PATH problem is back. When I run
>> C:\cygwin64\bin\fish.exe -l
>> I get the same error messages as before on startup, and PATH doesn't
>> include /bin /usr/bin /sbin /usr/sbin.
>> How are /bin /usr/bin etc. normally added to the PATH? I don't see any
>> logic to do it in /usr/share/fish/config.fish.
> That logic probably should be included.
> At least, bash does that in login files.
>
That was my conclusion as well*. Question is, should fish provide the
configuration, or should base-files cover all shells?
Andrew: thanks for confirming. If you're still looking for the logic and
where to put it, I suggested something in * as well.
Regards,
Dave.
* https://cygwin.com/ml/cygwin/2014-04/msg00175.html
--
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:[~2014-10-09 21:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-08 9:14 Andrew Schulman
2014-10-08 9:52 ` Alive4Ever
2014-10-08 9:58 ` Andrew Schulman
2014-10-08 10:08 ` Dave Kilroy
2014-10-08 17:37 ` Alive4Ever
2014-10-09 10:11 ` Dave Kilroy
2014-10-09 14:01 ` Andrew Schulman
2014-10-09 15:35 ` Andrey Repin
2014-10-09 16:44 ` Andrew Schulman
2014-10-09 17:35 ` Andrey Repin
2014-10-09 21:55 ` Dave Kilroy [this message]
2014-10-10 13:46 ` Andrew Schulman
2014-10-13 19:44 ` Dave Kilroy
2014-10-10 17:57 ` Achim Gratz
2014-10-09 18:01 ` fish PATH problem [ping Konrad] Andrew Schulman
2014-10-10 15:19 ` fish PATH problem Alive
2014-10-10 15:27 ` Andrew Schulman
2014-10-10 15:52 ` Alive
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=54370457.8060905@gmail.com \
--to=kilroyd@googlemail.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).