On 10/10/2014 14:46, Andrew Schulman wrote:
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
Dave Kilroy writes:
> That was my conclusion as well*. Question is, should fish provide the
> configuration, or should base-files cover all shells?
Since fish isn't in Base and deviates quite a bit from the "classic"
shells in its startup behaviour, I don't really think it would be
appropriate.
On 10/10/2014 22:27, Andrew Schulman wrote:
> Please try the updated fish 2.1.1 package I just posted, and see if it fixes
> those
> problems for you. Exit all running fish shells, then run:
>
> wget http://home.comcast.net/~andrex2/cygwin/$(arch)/fish-2.1.1-1.tar.xz
> tar -Jx -C/ -f fish-2.1.1-
> On 08/10/2014 17:08, Dave Kilroy wrote:
> > On 08/10/2014 10:57, Andrew Schulman wrote:
> >>> On Wednesday, October 08, 2014 05:13:54 AM Andrew Schulman wrote:
> When I try to start fish directly from the Windows shell instead of
> from
> bash, I get a boatload of errors, like this
On 08/10/2014 17:08, Dave Kilroy wrote:
> On 08/10/2014 10:57, Andrew Schulman wrote:
>>> On Wednesday, October 08, 2014 05:13:54 AM Andrew Schulman wrote:
When I try to start fish directly from the Windows shell instead of
from
bash, I get a boatload of errors, like this:
>>> I sugg
> 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 /bi
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
> So I just re-tested starting a fish login shell after updating cygwin64.
> As I suspected, fish has not been updated since the thread I quoted (Apr
> 2014), and the issue remains (with my install). Google doesn't show the
> maintainer on list since the announcement (Oct 2013), and his e-mail
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
> Greetings, Andrew Schulman!
>
> >> Andrew: appreciated if you can confirm whether simply invoking as a
> >> login shell works for you.
>
> > It sort of works. When I change my shell to /usr/bin/fish in /etc/passwd
> > and run
>
> > C:\cygwin64\bin\mintty.exe -
>
> > I don't get any error me
Greetings, Andrew Schulman!
>> Andrew: appreciated if you can confirm whether simply invoking as a
>> login shell works for you.
> It sort of works. When I change my shell to /usr/bin/fish in /etc/passwd
> and run
> C:\cygwin64\bin\mintty.exe -
> I don't get any error messages, as I first rep
> On 08/10/2014 18:36, Alive4Ever wrote:
> > On Wednesday, October 08, 2014 11:08:43 AM you wrote:
> >> Does that work. It seemed to have the same issue as noted in the
> >> following thread https://cygwin.com/ml/cygwin/2014-04/msg00111.html
> >>
> > It should work, although I don't recommend runni
On 08/10/2014 18:36, Alive4Ever wrote:
On Wednesday, October 08, 2014 11:08:43 AM you wrote:
Does that work. It seemed to have the same issue as noted in the
following thread https://cygwin.com/ml/cygwin/2014-04/msg00111.html
Dave.
It should work, although I don't recommend running cygwin apps
On Wednesday, October 08, 2014 11:08:43 AM you wrote:
> Does that work. It seemed to have the same issue as noted in the
> following thread https://cygwin.com/ml/cygwin/2014-04/msg00111.html
>
> Dave.
It should work, although I don't recommend running cygwin apps directly
via wincmd, unless the
On 08/10/2014 10:57, Andrew Schulman wrote:
On Wednesday, October 08, 2014 05:13:54 AM Andrew Schulman wrote:
When I try to start fish directly from the Windows shell instead of from
bash, I get a boatload of errors, like this:
I suggest you to read fish manual page, and find how to invoke fish
> On Wednesday, October 08, 2014 05:13:54 AM Andrew Schulman wrote:
> > When I try to start fish directly from the Windows shell instead of from
> > bash, I get a boatload of errors, like this:
>
> I suggest you to read fish manual page, and find how to invoke fish as login
> shell. On bash and z
On Wednesday, October 08, 2014 05:13:54 AM Andrew Schulman wrote:
> When I try to start fish directly from the Windows shell instead of from
> bash, I get a boatload of errors, like this:
>
> ===
> /usr/share/fish/functions/type.fish (line 14): if not getopt -T > /dev/null
>
When I try to start fish directly from the Windows shell instead of from
bash, I get a boatload of errors, like this:
===
/usr/share/fish/functions/type.fish (line 14): if not getopt -T > /dev/null
^
in function 'type',
called
18 matches
Mail list logo
