On 07/04/2014 13:02, Ronald Fischer wrote:
I have installed fish 2.1.0. Works fine, when invoking a new fish shell
manually.
However, when doing a
chere -ifcm -t mintty -s fish
and invoke the new fish shell from the Windows Explorer context menu, I
get plenty of error messages, like this:
<snip>
(more of this kind follow).
This looks like there is a problem the PATH, but this happens even when
I use the -2 on chere when installing the shell. Note that bash or zsh
shells installed via cygwin work fine.
In this 'broken' fish shell, I enter
echo $PATH; uname
and get the following output:
<snip>
/cygdrive/c/windows/system32 /cygdrive/c/windows
/cygdrive/c/windows/System32/Wbem
/cygdrive/c/windows/System32/WindowsPowerShell/v1.0
/cygdrive/c/windows/System32/WindowsPowerShell/v1.0 /cygdrive/c/Program
Files (x86)/Common Files/Citrix/System32 /cygdrive/c/Program Files
(x86)/Citrix/ICAService /cygdrive/c/Program Files (x86)/Citrix/System32
<snip>
To compare with, when I output the PATH from a "normal" fish shell (i.e.
one which I have invoked from, say, a bash shell), I get:
echo $PATH
.:/home/ronald.fischer/bin:/usr/local/bin:/usr/bin:/cygdrive/c/windows/system32:/cygdrive/c/windows:/cygdrive/c/windows/System32/Wbem:/cygdrive/c/windows/System32/WindowsPowerShell/v1.0:/cygdrive/c/windows/System32/WindowsPowerShell/v1.0:/cygdrive/c/Program
Files (x86)/Common Files/Citrix/System32:/cygdrive/c/Program Files
(x86)/Citrix/ICAService:/cygdrive/c/Program Files
(x86)/Citrix/System32:/usr/lib/lapack
We see that in fish, /usr/bin is missing from the PATH. This is strange,
in particular if I install chere fish with option -2, because in this
case, fish will be invoked via bash.
Ronald
Thanks for the report.
I've just checked my x86_64 and x86 installation. Things are working on
my installation as I have c:\cygwin\bin on my standard windows path.
When I remove it and invoke fish, I get the errors that you highlight.
Similarly when echo'ing $PATH under the broken fish, /usr/bin is not one
of the entries.
I need to have a play around to see how I can fix this, but I thought
cygwin prepended /usr/bin to the path...
Regards,
Dave.
--
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
