public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "Stephane.Carrez at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tui/11393] vi-mode keybindings don't work in TUI mode
Date: Sat, 10 Nov 2012 14:14:00 -0000	[thread overview]
Message-ID: <bug-11393-4717-o6IYB7zBGW@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-11393-4717@http.sourceware.org/bugzilla/>

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

Stephane Carrez <Stephane.Carrez at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2012-11-10
                 CC|                            |Stephane.Carrez at gmail
                   |                            |dot com
     Ever Confirmed|0                           |1

--- Comment #1 from Stephane Carrez <Stephane.Carrez at gmail dot com> 2012-11-10 14:14:20 UTC ---
Confirmed 7.5.

The problem comes from the TUI initialization that uses
the default readline keymap to setup specific key bindings.
Once we switch to TUI mode, we set our own keymap which comes from Emacs.

The TUI should manager a vi keymap override as it does for emacs
and detect which keymap is installed.

There is the issue of switching keymap when the TUI is active.

-- 
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:[~2012-11-10 14:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-11393-4717@http.sourceware.org/bugzilla/>
2012-03-19 19:43 ` scottt.tw at gmail dot com
2012-11-10 14:14 ` Stephane.Carrez at gmail dot com [this message]
2021-04-02 19:55 ` 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-11393-4717-o6IYB7zBGW@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).