Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.bugs.dist > #1208195

Bug#708979: closed by Gioele Barabucci <gioele@svario.it> (Re: Bug#708979: bash (readline): Something is wrong with binding keys to functions)

Show all headers | View raw

[Multipart message — attachments visible in raw view] - view raw

On Tue, 13 Aug 2024 at 15:13, Vincent Lefevre <vincent@vinc17.net> wrote:

>
> For \M-p and \M-n, this may be a documentation inaccuracy. The
> readline(3readline) man page says
>
>   An Emacs-style notation is used to denote keystrokes.  Control keys are
>   denoted by C-key, e.g., C-n means Control-N.  Similarly, meta keys  are
>   denoted  by  M-key,  so M-x means Meta-X.  (On keyboards without a meta
>   key, M-x means ESC x, i.e., press the Escape key then the x key.   This
>   makes  ESC the meta prefix.  The combination M-C-x means ESC-Control-x,
>   or press the Escape key then hold the Control key while pressing the  x
>   key.)
>
> However, even if the keyboard has a Meta key, it has the effect to
> generate an Escape character, so that one should use the \e form in
> the .inputrc file.


I'm not quite sure I understand you here: are you saying that it's
documented somewhere that one should use the "\e" form? Or is this just
your assertion, in which case, on what do you base it?


> For instance, with
>
> "\ep": history-search-backward
>
> M-p does a history-search-backward with libreadline8 (I've tried with
> gp from the pari-gp package).
>

As I said, I tried something similar.

Perhaps readline should make \M- equivalent to \e for the .inputrc
> file.
>

As I said in my original report, "\M-" worked fine in readline 5.0. So as
far as I can tell, it's a regression.

In any case, I can't see any sense in requiring \e for some keys and not
others.

In any case, sounds like the issue should go upstream at this point?

-- 
https://rrt.sc3d.org

Back to linux.debian.bugs.dist | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Bug#708979: closed by Gioele Barabucci <gioele@svario.it> (Re: Bug#708979: bash (readline): Something is wrong with binding keys to functions) Reuben Thomas <rrt@sc3d.org> - 2024-08-10 17:00 +0200
  Bug#708979: closed by Gioele Barabucci <gioele@svario.it> (Re: Bug#708979: bash (readline): Something is wrong with binding keys to functions) Vincent Lefevre <vincent@vinc17.net> - 2024-08-13 16:20 +0200
    Bug#708979: closed by Gioele Barabucci <gioele@svario.it> (Re: Bug#708979: bash (readline): Something is wrong with binding keys to functions) Reuben Thomas <rrt@sc3d.org> - 2024-08-13 17:40 +0200
      Bug#708979: closed by Gioele Barabucci <gioele@svario.it> (Re: Bug#708979: bash (readline): Something is wrong with binding keys to functions) Vincent Lefevre <vincent@vinc17.net> - 2024-08-13 18:50 +0200
        Bug#708979: closed by Gioele Barabucci <gioele@svario.it> (Re: Bug#708979: bash (readline): Something is wrong with binding keys to functions) Vincent Lefevre <vincent@vinc17.net> - 2024-08-13 19:00 +0200
        Bug#708979: closed by Gioele Barabucci <gioele@svario.it> (Re: Bug#708979: bash (readline): Something is wrong with binding keys to functions) Reuben Thomas <rrt@sc3d.org> - 2024-08-13 19:50 +0200

csiph-web