Chet Ramey wrote:
> By default, readline binds the tty editing characters (erase, kill,
> [...]
Use the `bind-tty-special-characters' variable to enable or disable this
> behavior.
>
Thanks. That does indeed address my issue.
I understand and appreciate using the tty editing bindings by default
Chet Ramey wrote:
> Bob Proulx wrote:
> >Normally control-u is bound to tty driver kill. Because of there is a
> >tty driver value for ^U that value always overrides any readline
> >binding. But if ^U is remove from the tty driver setting then it
> >won't.
>
> Note that undefining a tty editing
Bob Proulx wrote:
Normally control-u is bound to tty driver kill. Because of there is a
tty driver value for ^U that value always overrides any readline
binding. But if ^U is remove from the tty driver setting then it
won't.
There isn't a portable way to unset these values in the tty driver b
Chet Ramey wrote:
> Woody Thrower wrote:
> >It appears that bash cannot bind ctrl-u either by using the "bind" command,
> >or by reading .inputrc at startup.
>
> By default, readline binds the tty editing characters (erase, kill,
> literal-next, word-erase) to their readline equivalents when it's
Woody Thrower wrote:
It appears that bash cannot bind ctrl-u either by using the "bind" command,
or by reading .inputrc at startup.
By default, readline binds the tty editing characters (erase, kill,
literal-next, word-erase) to their readline equivalents when it's called,
if they're bound to r
