public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "memo.salas at gmail 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, 08 Jun 2015 06:53:00 -0000	[thread overview]
Message-ID: <bug-15163-4717-vKuh3XNvM0@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-15163-4717@http.sourceware.org/bugzilla/>

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

--- Comment #5 from Memo Salas <memo.salas at gmail dot com> ---
I changed my workaround by to not hard-code a key combination for exiting the
tui mode, and instead pick up a key combination from the ~/.inputrc file, , by
modifying the function tui_initialize_readline to call rl_re_read_init_file (in
readline/bind.c) before returning.

My ~/.inputrc now has a keyboard mapping to associate to "tui-switch-mode".
Regardless, for a better out-of-the-box experience perhaps a better default for
vi key bindings is needed, at least for "tui-switch-mode", then things would
work without requiring users to modify ~/.inputrc or similar.

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


  parent reply	other threads:[~2015-06-08  6:53 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 [this message]
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-vKuh3XNvM0@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).