On 8/5/16 11:16 AM, John Passaro wrote:
> Bash Version: 4.3
> Patch Level: 42
> Release Status: release
>
> Description:
> In an interactive session, when attempting file completion via <Tab>
> when a certain type of ill-formed command substitution is present, bash
> gives verbose error output relating to "unexpected end of file".
>
> Naturally you can work around this by never making this mistake when
> using command substitution, but it seems to me bash can probably guard
> for this and avoid disruptive error messages.
Thanks for the report. Bash can avoid the error messages on an incomplete
word expansion, such as the one in your example.
Chet
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU c...@case.edu http://cnswww.cns.cwru.edu/~chet/
