On Sat, Jun 06, 2015, Paul wrote:
> On Saturday, June 6, 2015 at 11:24:25 PM UTC-4, Eric Christopherson
> wrote:
> > On Sat, Jun 06, 2015, Paul wrote:
> >> I don't find that my vimrc settings take effect when using vi
> >> editing mode in readline. However, I can use the fc commad to
> >> switch into full fledged vim. Googling hasn't clarified whether it
> >> is built-in to bash or a separate command (there's info indicating
> >> both cases). In Cygwin, it seems to be a separate executable, so
> >> not part of bash.
> >
> > You can tell for sure what kind of command fc is with
> >
> > type fc
> >
> > in the shell. For me it outputs "fc is a shell builtin". There's a
> > shortcut, though: hitting Ctrl-X Ctrl-E on any line will bring up an
> > editor for that particular line, like fc does. I think it also uses
> > the same environment variables as fc does to determine which editor
> > to launch.
>
> Actually, I'm blind. I did in fact use "type -a" and what came back
> was
>
> fc is a shell builtin
> fc is /c/Windows/system32/fc
>
> The Windows version does something completely unrelated.
>
> As for Ctrl-X Ctrl-E, it doesn't do anything in my setup.
That's strange. I don't have it explicitly enabled in .inputrc, but
`bind -p` shows it as
"\C-x\C-e": edit-and-execute-command
So you should be able to add that to your .inputrc. Or pick a key
binding that suits you better.
--
Eric Christopherson
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
"vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
