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


Groups > gnu.bash.bug > #14937 > unrolled thread

readline fails to understand options.

Started byBize Ma <binaryzebra@gmail.com>
First post2018-12-21 00:52 -0500
Last post2018-12-21 00:52 -0500
Articles 1 — 1 participant

Back to article view | Back to gnu.bash.bug


Contents

  readline fails to understand options. Bize Ma <binaryzebra@gmail.com> - 2018-12-21 00:52 -0500

#14937 — readline fails to understand options.

FromBize Ma <binaryzebra@gmail.com>
Date2018-12-21 00:52 -0500
Subjectreadline fails to understand options.
Message-ID<mailman.6036.1545371542.1284.bug-bash@gnu.org>
This works:

     $ bind 'set enable-bracketed-paste on'; bind -v | grep 'bracketed'
     set enable-bracketed-paste on

However, almost any variation of the parameter "on" is not understood by
readline:

     $ bind 'set enable-bracketed-paste on .'; bind -v | grep 'bracketed'
     set enable-bracketed-paste off

     $ bind 'set enable-bracketed-paste "on"'; bind -v | grep 'bracketed'
     set enable-bracketed-paste off

Without any error or warning !!

It appears to fall to default value, while this:

     $ bind 'set bell-style on' ; bind -v | grep 'bell-style'
     set bell-style audible

     $ bind 'set bell-style onf' ; bind -v | grep 'bell-style'
     set bell-style audible

Stays at its last value.

It seems that the parser for this options is unable to process anything
after a valid parameter. And it doesn't emit an error or warning either.

Since the parser needs some improvement: Could it be possible to add the
capability to detect  a `#` after the options as a comment ?

Please read:
https://unix.stackexchange.com/questions/487037/why-is-my-readline-inputrc-configuration-being-ignored/487285#487285

[toc] | [standalone]


Back to top | Article view | gnu.bash.bug


csiph-web