It is working properly for me now (with and without oh-my-fish). Sorry for the false alarm. Using the most recent build solved the issue I was experiencing.
Worth noting that my parallel script was using git+ssh to remote servers that had an older version of fish as the default shell and that was what was giving the error message. When I switched to bash (as well as when I upgraded fish to a build from master on the remote machine) the problem went away. On Mon, Mar 17, 2014 at 2:12 PM, Glen Marchesani <g...@model3.net> wrote: > > I did a quick thing that I thought would remove oh-my-fish but I still get > an error with oh my fish in the stack trace. So I will setup a vanilla > user to repro this (i.e. one with just fish and only fish). > > > > On Mon, Mar 17, 2014 at 2:03 PM, Siteshwar <sitesh...@gmail.com> wrote: > >> Hi Glen, >> >> Your logs show that you have oh-my-fish installed on your system. Can you >> test if the issue reproduces if you don't have oh-my-fish installed on your >> system ? >> > > > > -- > Glen Marchesani > Chief Architect | Emeris Software > 423-454-9199 | g...@model3.net > > -- Glen Marchesani Chief Architect | Emeris Software 423-454-9199 | g...@model3.net
------------------------------------------------------------------------------
_______________________________________________ Fish-users mailing list Fish-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fish-users
