Re: Tokenizer problem affecting argument history

[Chet Ramey]

On 2/23/17 5:58 AM, ecki@tofex.de wrote:
> Configuration Information [Automatically generated, do not change]:
> Machine: x86_64
> OS: linux-gnu
> Compiler: x86_64-pc-linux-gnu-gcc
> Compilation CFLAGS:  -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64' 
> -DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_64-pc-linux-gnu' 
> -DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACKAGE='bash' -DSHELL 
> -DHAVE_CONFIG_H   -I. -I./include -I. -I./include -I./lib  
> -DDEFAULT_PATH_VALUE='/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin'
>  -DSTANDARD_UTILS_PATH='/bin:/usr/bin:/sbin:/usr/sbin' 
> -DSYS_BASHRC='/etc/bash/bashrc' -DSYS_BASH_LOGOUT='/etc/bash/bash_logout' 
> -DNON_INTERACTIVE_LOGIN_SHELLS -DSSH_SOURCE_BASHRC -DUSE_MKTEMP -DUSE_MKSTEMP 
> -march=corei7 -O2 -pipe
> uname output: Linux lokalhorst.net.tofex.de 4.4.0-gentoo-r1 #1 SMP Mon Jan 25 
> 18:18:38 CET 2016 x86_64 Intel(R) Core(TM) i7-3770S CPU @ 3.10GHz 
> GenuineIntel GNU/Linux
> Machine Type: x86_64-pc-linux-gnu
> 
> Bash Version: 4.3
> Patch Level: 48
> Release Status: release
> 
> Description:
>       When evaluating complex commands containing "$()" expressions, and later
>       accessing arguments with !$, !* or !:<num>, results are not as expected,
>       as the "$()" expression is broken into non-executable parts (see below).
> 
>       At least the manpage should clearly state such behaviour - I didn't find
>       that within 10 minute search.
> 
> Repeat-By:
>       $ mkdir -p /tmp/Step1
>       $ ls /$(echo tmp)/Step1
>       ...
>       $ echo !:*
>       echo /$ ( echo tmp ) /Step1
>       bash: syntax error near unexpected token `('

The history library knows very little shell syntax.

-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer
                 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU    chet@case.edu    http://cnswww.cns.cwru.edu/~chet/