vi mode? #3
Comments
|
Added a pull request |
tadmarshall
pushed a commit
to tadmarshall/linenoise
that referenced
this issue
Oct 18, 2011
…xceptions Fix first-chance exceptions in Windows A call to WriteConsoleOutputCharacter() didn't have its final parameter set, passing a zero instead of a pointer to where to return the char count. I added the same code that was there for FillConsoleOutputCharacter() and FillConsoleOutputAttribute(), just allocate a dummy 'n' and pass its address.
andreas-kupries
referenced
this issue
in andreas-kupries/linenoise
Feb 19, 2013
…tion Clarify the comment at the definition of IGNORE_RC.
|
The best feature would be is to have vim mappings. Then I can throw away my .inputrc and start using some imap and nmap shortcuts for all my abbreviated commands. Bash with normal mode would make the command line as productive as the editor. :) |
|
+1 Thank you @bobrippling for your patch - it adds support basically for the whole vi mode, which is awesome! Actually those 150 new lines are imho definitely worth including this patch into this original repository. |
|
+1 This would be a fantastic improvement from my point of view, as I'm using another project (Planck) that uses linenoise. Is anything blocking the pull request from being merged? Thanks! |
|
This issue is addressed by #92. |
|
Looks like #92 just got close without merging 😞 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This would seriously up the line count, but I'm also an addict that can't get enough of vi/vim.
Some knowledge of modes, with support for Esc, i, h, l, j & k are the minimal requirements.
The text was updated successfully, but these errors were encountered: