I've done 2 very small pull requests:
https://github.com/fish-shell/fish-shell/pull/220
https://github.com/fish-shell/fish-shell/pull/221
I was about to add documentation for the echo builtin... but then I
realized that it has already been written and it's there in my local
checkout, so
On 9 July 2012 04:16, Kevin Ballard ke...@sb.org wrote:
What should be documented? The fact that running commands overwrites $status?
obviously not: I'm talking about the fact that $status behaves like a
global variable that gets rebinded locally in every function
On 9 July 2012 22:14, David Frascone d...@frascone.com wrote:
$status, like $? in bash, will be overwritten by EVERY command executed.
So, given an abridged version of your example:
codemonkey@monkeytree ~/W/grive function dummy
nonexistant command
What should be documented? The fact that running commands overwrites $status?
-Kevin
On Jul 8, 2012, at 8:59 AM, Dario Bertini berda...@gmail.com wrote:
On 1 July 2012 23:14, ridiculous_fish corydo...@ridiculousfish.com wrote:
I wasn't able to reproduce this. If you share your fish_prompt
I wasn't able to reproduce this. If you share your fish_prompt function, I can
dig into it a bit more.
_fish
On Jun 21, 2012, at 5:23 PM, Dario Bertini wrote:
In my fish_prompt function I added the $status variable, to let me
instantly know the exit code of the last command I run (like in
In my fish_prompt function I added the $status variable, to let me
instantly know the exit code of the last command I run (like in the
old prompt I was using on zsh)
but in my prompt, the value is always stuck to 0
is someone else able to reproduce it? is it a known behaviour? is it a bug?
On 22 June 2012 02:43, Tom W. Most tomm...@gmail.com wrote:
It works for me, but of course it does need to be referenced in the
first statement in the prompt. This is my prompt:
Thank you, it works...
but it seems a bit unintuitive that it has to be the first statement:
I mean, fish_prompt
