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