public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "rhys.ulerich at gmail dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug tui/15163] New: Vi settings within ~/.inputrc prevent entering/exiting TUI via C-x a Date: Wed, 20 Feb 2013 16:51:00 -0000 [thread overview] Message-ID: <bug-15163-4717@http.sourceware.org/bugzilla/> (raw) http://sourceware.org/bugzilla/show_bug.cgi?id=15163 Bug #: 15163 Summary: Vi settings within ~/.inputrc prevent entering/exiting TUI via C-x a Product: gdb Version: 7.5 Status: NEW Severity: normal Priority: P2 Component: tui AssignedTo: unassigned@sourceware.org ReportedBy: rhys.ulerich@gmail.com Classification: Unclassified Having vi-like settings in ~/.inputrc breaks entering/exiting TUI mode using C-x a or any other key combination documented at http://sourceware.org/gdb/download/onlinedocs/gdb/TUI-Keys.html. To reproduce: 1. Remove any ~/.inputrc file. 2. Run 'gdb' 3. Hit C-x a and observe TUI mode starting. 4. Quit gdb 5. Create a ~/.inputrc file containing two lines: > set editing-mode vi > set keymap vi 6. Run 'gdb' 7. Hit C-x a and observe ^X^A being echoed to the screen but TUI mode not starting. I am unaware of any gdb command that will enter/exit TUI mode independently of the key combination. Is there one? Observed generally throughout 7.x and reproduced just now on 7.5.1. - Rhys -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
next reply other threads:[~2013-02-20 16:51 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-02-20 16:51 rhys.ulerich at gmail dot com [this message] 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 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@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).