On 5/27/14, 1:19 AM, fargred@home wrote:
> Bash Version: 4.2
> Patch Level: 45
> Release Status: release
>
> Description:
> The syntax of the ‘bind’ builtin command suggests that any readline
> command may be executed just by passing command name to the ‘bind’ in
> accordance with ‘man bash’. However,
>
> bind shell-expand-line
That's a fairly creative reading of the manual page, since the description
of the bind builtin begins:
Display current readline key and function bindings, bind a key
sequence to a readline function or macro, or set a readline
variable.
>
> Doesn’t seem to be working, as well as alias-expand-line or
> history-and-alias-expand-line. Strange bug is, after executing the command
> above the lowercase ‘l’ cannot be typed into terminal (That doesn’t
> affect uppercase ‘l’ or letters on the other layout). No, I do not have
> any aliases like ‘l’, it stops working even if you
> start a new shell with an empty environment
Sure, since you've just managed to unbind all of the characters in that
command (you didn't provide a command name to bind them to).
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/
