public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Andrew Schulman <schulman.andrew@epa.gov>
To: cygwin@cygwin.com
Subject: Re: fish PATH problem
Date: Fri, 10 Oct 2014 13:46:00 -0000	[thread overview]
Message-ID: <vijf3adncvnnu3b0dh9h8qbjk4i58p0b8d@4ax.com> (raw)
In-Reply-To: <54370457.8060905@gmail.com>

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

OK, I rolled a new release of fish 2.1.1:

x86:
http://home.comcast.net/~andrex2/cygwin/x86/fish-2.1.1-1.tar.xz
http://home.comcast.net/~andrex2/cygwin/x86/fish-2.1.1-1-src.tar.xz

x86_64:
http://home.comcast.net/~andrex2/cygwin/x86_64/fish-2.1.1-1.tar.xz
http://home.comcast.net/~andrex2/cygwin/x86_64/fish-2.1.1-1-src.tar.xz

It adds the following improvements in /etc/fish/config.fish:

* Prepends /usr/local/bin /bin to PATH.  This solves the PATH errors for me.

* Changes to the home directory in login shells.

* sources all scripts /etc/profile.d/*.fish.  So far I think there are few or none of
those, but once fish supports them, some will start to appear, especially if we can
get cygport to start creating them.

I think that's the best answer to your question about base-files.  I looked in
/etc/profile to see if it might be made to support fish too, but I don't think so.
It's too sh-centric.  fish's syntax is too different.  So if fish supports
/etc/profile.d on its own, then we can just leave it at that.

Please try it out, and let me know how it works for you.  If it's okay and if Konrad
doesn't answer, then I'll adopt the package and put out the new release.  I've
switched to using fish as my default shell now, so I want to see it maintained.

Andrew


--
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

  reply	other threads:[~2014-10-10 13:46 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
2014-10-10 13:46                     ` Andrew Schulman [this message]
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=vijf3adncvnnu3b0dh9h8qbjk4i58p0b8d@4ax.com \
    --to=schulman.andrew@epa.gov \
    --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).