Dieter Holkenpolk wrote:
> bash-4.0$ a () { bind '"\C-w": unix-filename-rubout'; }
> bash-4.0$ b () { bind -p | grep 'unix.*rubout'; }
> bash-4.0$ a; b
> "\C-w": unix-filename-rubout
> # unix-word-rubout (not bound)
> bash-4.0$ b
> # unix-filename-rubout (not bound)
> "\C-w": unix-word-rubout
> bash-4.0$
>
> Same in bash-3.2.
The last time this came up, I wrote:
Beginning with bash-3.0, after a number of requests for the feature,
readline began "honoring" the terminal special characters by binding
them to their readline equivalents at startup.
In bash-3.1, this was made dependent on the value of the readline variable
`bind-tty-special-chars', which is on by default.
Chet
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, ITS, CWRU c...@case.edu http://cnswww.cns.cwru.edu/~chet/
