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 13:02:00 -0000	[thread overview]
Message-ID: <bug-15163-4717-GqhZ9u57sa@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-15163-4717@http.sourceware.org/bugzilla/>

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

Pedro Alves <palves at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |WAITING
                 CC|                            |palves at redhat dot com

--- Comment #1 from Pedro Alves <palves at redhat dot com> 2013-02-25 13:02:25 UTC ---
> I am unaware of any gdb command that will enter/exit TUI mode independently of
the key combination.  Is there one?

Commands like "tui foo", and "layout next" enter the TUI.

I'm not aware of any GDB command to exit the TUI, and looking at the code, I
can't find any that would do it as side effect.

However, TUI enter/exit is bound to the readline "tui-switch-mode"
command/function:

>  rl_add_defun ("tui-switch-mode", tui_rl_switch_mode, -1);

One should be able to use that to bind any key combo to TUI enter/exit in the
inputrc file, per the "Key Bindings" node in the readline manual.  However, I'm
not familiar readline's vi mode (emacs user here), and whether key bindings
apply in that mode.

Let me know if that helps.

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


  reply	other threads:[~2013-02-25 13:02 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 ` palves at redhat dot com [this message]
2013-02-25 16:18 ` [Bug tui/15163] " 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-GqhZ9u57sa@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).