This is the mail archive of the gdb-prs@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug tui/15163] Vi settings within ~/.inputrc prevent entering/exiting TUI via C-x a


https://sourceware.org/bugzilla/show_bug.cgi?id=15163

Oliver Kiddle <okiddle at yahoo dot co.uk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |okiddle at yahoo dot co.uk

--- Comment #7 from Oliver Kiddle <okiddle at yahoo dot co.uk> ---
Not being able to bind ^X,s in vi-mode is perhaps related to ^X alone being
bound to self-insert. In any case, I think you're asking the wrong question.
Key sequences starting with Ctrl-X is really an emacs thing. What you should be
asking is what a natural key combination in vi-mode would be.

I would instead suggest binding a sequence starting with a backslash in vi
command mode. This is perhaps more of a vim convention. If you want to look at
the vim documentation, see :help leader. <Leader> is a special token in vim key
bindings and is a common prefix for keys used by plugins and user
configuration. Some people redefine leader to, e.g. comma but comma does have a
use even in original vi.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]