Path: csiph.com!goblin1!goblin.stu.neva.ru!usenet.stanford.edu!not-for-mail
From: Bize Ma <binaryzebra@gmail.com>
Newsgroups: gnu.bash.bug
Subject: readline fails to understand options.
Date: Fri, 21 Dec 2018 00:52:07 -0500
Lines: 34
Approved: bug-bash@gnu.org
Message-ID: <mailman.6036.1545371542.1284.bug-bash@gnu.org>
NNTP-Posting-Host: lists.gnu.org
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
To: Chester Ramey <chet.ramey@case.edu>, bug-bash <bug-bash@gnu.org>
Envelope-to: bug-bash@gnu.org
Precedence: list
Xref: csiph.com gnu.bash.bug:14937

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