public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "vz-sourceware at zeitlins dot org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug tui/15163] Vi settings within ~/.inputrc prevent entering/exiting TUI via C-x a Date: Sun, 26 Jul 2015 21:45:00 -0000 [thread overview] Message-ID: <bug-15163-4717-9gXbh31fWl@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-15163-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=15163 Vadim Zeitlin <vz-sourceware at zeitlins dot org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |vz-sourceware at zeitlins dot org --- Comment #6 from Vadim Zeitlin <vz-sourceware at zeitlins dot org> --- Notice that even when using `gdb -tui` to start gdb in TUI mode, it's impossible to switch to the single key mode as `^X,s` doesn't work with vi bindings neither. Using `<Esc>,^E` does help but as the bindings reset to vi mode when you exit the single key mode, you need to redo it every time which makes the single key mode just not worth it -- even having a command like "tui single-key" would be faster than doing this, but unfortunately gdb doesn't seem to provide anything like this. Is there any workaround that would allow to use keys starting with `^X` in vi mode? -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2015-07-26 21:45 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-02-20 16:51 [Bug tui/15163] New: " rhys.ulerich at gmail dot com 2013-02-25 13:02 ` [Bug tui/15163] " palves at redhat dot com 2013-02-25 16:18 ` rhys.ulerich at gmail dot com 2013-02-25 18:56 ` palves at redhat dot com 2015-06-05 2:11 ` memo.salas at gmail dot com 2015-06-08 6:53 ` memo.salas at gmail dot com 2015-07-26 21:45 ` vz-sourceware at zeitlins dot org [this message] 2020-04-12 23:02 ` thib at stammed dot net 2021-04-02 19:56 ` tromey at sourceware dot org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-15163-4717-9gXbh31fWl@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).