public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "palves at redhat dot com" <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: Mon, 25 Feb 2013 18:56:00 -0000	[thread overview]
Message-ID: <bug-15163-4717-kHAnW4QujJ@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-15163-4717@http.sourceware.org/bugzilla/>

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

--- Comment #3 from Pedro Alves <palves at redhat dot com> 2013-02-25 18:56:00 UTC ---
I'm afraid at this point I don't really know if there's a bug, or if there is,
if it is GDB specific.  As mentioned, I'm blissfully ignorant on vi things.
However, I'd think that if bash can handle the same style of key bindings in vi
mode, then gdb should too.  What does bash do?

> (though this is likely me being an idiot).

:-)  Most probably not.

A gdb command to toggle the TUI off seems like something nice to have, as
escape hatch out of broken-beyond-repair terminal settings though.

-- 
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.


  parent reply	other threads:[~2013-02-25 18:56 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 [this message]
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-kHAnW4QujJ@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: link
Be 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).