During the process of porting __git_ps1 to Fish (see my previous email), I ran
into lots of issues (both design issues and missing functionality) with Fish
scripting. I've already filed issues for a lot of these, but I thought I would
just try to round them all up. These are in no particular
Ian, thank you for tackling this!! vi mode is highly desired by other users,
but I don't know enough about it to implement it.
Regarding repainting, does 'commandline -f repaint' work?
_fish
On Jun 21, 2012, at 12:03 AM, Ian Munsie wrote:
your vi-mode works wonderful.
I've only the problem
I have created a simple vim script for fish highlighting
I have added fish keywords to 'sh'. (so it's based on sh filetype)
and your auto commenting plugin will work for fish files
script is here:
http://www.vim.org/scripts/script.php?script_id=4106
Hello Kevin,
Thank you for taking the time to write this up! Your git script looks very
ambitious, and so this is thoughtful, informed feedback. (Incidentally I just
merged your git script changes). Let me respond to each point in turn:
1.2. 3.: Regarding string manipulation: I'm in favor of
On Thu, Jun 21, 2012 at 8:50 PM, Kevin Ballard ke...@sb.org wrote:
I don't seem to be receiving my own messages sent to this list, even
though I
triple-checked my settings and I'm supposed to be getting them. Is anyone
else
having this problem?
I didn't even know I was supposed to receive
Regarding repainting, does 'commandline -f repaint' work?
It seems that I need both commandline -f repaint and bind ''
self-insert for it to work.
I'm wondering if the repaint command never goes through without the
default binding set - I tried binding just \xe027 (R_REPAINT if I
added that up
Hi, I recently started to use fishfish... I'm a bzr user (but
obviously also an hg and git one) and I read a previous mail about it
(I cannot reply to it since I wasn't subscribed to the list at the
time)
From the homepage, I assumed that the completion was done by reading
the man pages on the
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
This can be demonstrated with something like:
echo howdy hicontrol-w
echo howdy Ialt-b
Previously this would delete/move all the way to the start of 'howdy',
rather than just the word 'hi'/'I'.
It seems that the code to ignore the character under the cursor was
redundant, as all the cases I've
I'd love to see some mercurial toys, like the git and bzr ones I've seen .
. . maybe I'll hack something together if I find some time.
On Thu, Jun 21, 2012 at 6:16 PM, Dario Bertini berda...@gmail.com wrote:
Hi, I recently started to use fishfish... I'm a bzr user (but
obviously also an hg and
11 matches
Mail list logo