Debian Bug report logs -
#198634
Can't bind keys in insert mode?
Reported by: "Marcelo E. Magallon" <mmagallo@debian.org>
Date: Tue, 24 Jun 2003 15:48:04 UTC
Severity: wishlist
Tags: upstream
Fixed in version 5.2+dfsg-3+rm
Done: Debian FTP Masters <ftpmaster@ftp-master.debian.org>
Bug is archived. No further changes may be made.
Forwarded to chet@po.cwru.edu
Toggle useless messages
Report forwarded to debian-bugs-dist@lists.debian.org, Matthias Klose <doko@debian.org>:
Bug#198634; Package libreadline4.
(full text, mbox, link).
Acknowledgement sent to "Marcelo E. Magallon" <mmagallo@debian.org>:
New Bug report received and forwarded. Copy sent to Matthias Klose <doko@debian.org>.
(full text, mbox, link).
Message #5 received at submit@bugs.debian.org (full text, mbox, reply):
Package: libreadline4
Version: 4.3-5
Severity: wishlist
Hi,
just for fun I switched the editing mode to vi style. One thing I
noticed rather quickly is that C-l in _insert_ mode produces a ^L
character, instead of issuing the clear-screen command. Looking at the
documentation I can't figure out if this is a feature or a bug. From
the docs it reads:
While the Readline library does not have a full set of `vi'
editing functions, it does contain enough to allow simple editing
of the line. The Readline `vi' mode behaves as specified in the
POSIX 1003.2 standard.
In order to switch interactively between `emacs' and `vi' editing
modes, use the command `M-C-j' (bound to emacs-editing-mode when
in `vi' mode and to vi-editing-mode in `emacs' mode). The
Readline default is `emacs' mode.
When you enter a line in `vi' mode, you are already placed in
`insertion' mode, as if you had typed an `i'. Pressing <ESC>
switches you into `command' mode, where you can edit the text of
the line with the standard `vi' movement keys, move to previous
history lines with `k' and subsequent lines with `j', and so
forth.
and that's pretty much it. I suspect the last sentence in the first
paragraph might have something to do with this, but that's just a
guess. If this is really a feature, could it be documented a _bit_
more verbosely somewhere please?
Oh, btw, I can't get C-M-j to work. Perhaps I need to figure out which
key is Meta. I thought it was "Alt" (which xkeycaps confirms), but no
cigar...
-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux techno 2.4.21-ck1 #1 Mon Jun 16 09:59:43 CEST 2003 i686
Locale: LANG=3DC, LC_CTYPE=3Den_US
Versions of packages libreadline4 depends on:
ii libc6 2.3.1-17 GNU C Library: Shared librarie=
s an
ii libncurses5 5.3.20030510-2 Shared libraries for terminal =
hand
-- no debconf information
Tags added: upstream
Request was from Matthias Klose <doko@cs.tu-berlin.de>
to control@bugs.debian.org.
(full text, mbox, link).
Noted your statement that Bug has been forwarded to chet@po.cwru.edu.
Request was from Matthias Klose <doko@cs.tu-berlin.de>
to control@bugs.debian.org.
(full text, mbox, link).
Information forwarded to debian-bugs-dist@lists.debian.org, Matthias Klose <doko@debian.org>:
Bug#198634; Package libreadline4.
(full text, mbox, link).
Acknowledgement sent to chet@cwru.edu:
Extra info received and forwarded to list. Copy sent to Matthias Klose <doko@debian.org>.
(full text, mbox, link).
Message #14 received at 198634@bugs.debian.org (full text, mbox, reply):
> Package: libreadline4
> Version: 4.3-5
> Severity: wishlist
>
> Hi,
>
> just for fun I switched the editing mode to vi style. One thing I
> noticed rather quickly is that C-l in _insert_ mode produces a ^L
> character, instead of issuing the clear-screen command. Looking at the
> documentation I can't figure out if this is a feature or a bug.
The Bash/readline vi editing mode follows the POSIX.2 standard for the
vi editing mode included in the description of `sh'.
(http://www.opengroup.org/onlinepubs/007904975/utilities/sh.html)
That description requires ^L to be mapped to self-insert in vi insert mode.
> When you enter a line in `vi' mode, you are already placed in
> `insertion' mode, as if you had typed an `i'. Pressing <ESC>
> switches you into `command' mode, where you can edit the text of
> the line with the standard `vi' movement keys, move to previous
> history lines with `k' and subsequent lines with `j', and so
> forth.
>
> and that's pretty much it. I suspect the last sentence in the first
> paragraph might have something to do with this, but that's just a
> guess. If this is really a feature, could it be documented a _bit_
> more verbosely somewhere please?
http://www.opengroup.org/onlinepubs/007904975/utilities/sh.html#tag_04_128_13_03
> Oh, btw, I can't get C-M-j to work. Perhaps I need to figure out which
> key is Meta. I thought it was "Alt" (which xkeycaps confirms), but no
> cigar...
It doesn't work in bash. Bash disables it because `set -o emacs' and
`set -o vi' exist. There is text in the readline manual that is conditionally
included depending on whether or not the text is part of the bash manual
or standalone. The standalone version includes the M-C-j stuff; the bash
version includes `set -o {emacs,vi}'.
Chet
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
( ``Discere est Dolere'' -- chet )
Live...Laugh...Love
Chet Ramey, ITS, CWRU chet@po.cwru.edu http://tiswww.tis.cwru.edu/~chet/
Information forwarded
to debian-bugs-dist@lists.debian.org, Matthias Klose <doko@debian.org>:
Bug#198634; Package libreadline5.
(Tue, 23 Feb 2010 01:48:03 GMT) (full text, mbox, link).
Acknowledgement sent
to Marcelo <marcelo.magallon@gmail.com>:
Extra info received and forwarded to list. Copy sent to Matthias Klose <doko@debian.org>.
(Tue, 23 Feb 2010 01:48:03 GMT) (full text, mbox, link).
Message #21 received at 198634@bugs.debian.org (full text, mbox, reply):
Just for the record, this configuration in ~/.inputrc does the trick:
set keymap vi-insert
Control-L: clear-screen
set editing-mode vi
AFAICS it's still not documented.
Marcelo
Reply sent
to Debian FTP Masters <ftpmaster@ftp-master.debian.org>:
You have taken responsibility.
(Mon, 01 Feb 2021 22:21:08 GMT) (full text, mbox, link).
Notification sent
to "Marcelo E. Magallon" <mmagallo@debian.org>:
Bug acknowledged by developer.
(Mon, 01 Feb 2021 22:21:08 GMT) (full text, mbox, link).
Message #26 received at 198634-done@bugs.debian.org (full text, mbox, reply):
Version: 5.2+dfsg-3+rm
Dear submitter,
as the package readline5 has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/980504
The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.
Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmaster@ftp-master.debian.org.
Debian distribution maintenance software
pp.
Joerg Jaspert (the ftpmaster behind the curtain)
Bug archived.
Request was from Debbugs Internal Request <owner@bugs.debian.org>
to internal_control@bugs.debian.org.
(Tue, 02 Mar 2021 07:31:24 GMT) (full text, mbox, link).
Send a report that this bug log contains spam.
Debian bug tracking system administrator <owner@bugs.debian.org>.
Last modified:
Wed Dec 6 07:27:15 2023;
Machine Name:
bembo
Debian Bug tracking system
Debbugs is free software and licensed under the terms of the GNU
Public License version 2. The current version can be obtained
from https://bugs.debian.org/debbugs-source/.
Copyright © 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson,
2005-2017 Don Armstrong, and many other contributors.