Subject: bug#29157: 25.3; Eshell parsing fails sometimes, e.g. "date" and "sed"

From: Noam Postavsky <[email-masked]>
Date: Thu, 09 Nov 2017 21:04:13 -0500

Andreas Schwab <[email-masked]> writes:

> On Nov 05 2017, Noam Postavsky <[email-masked]> wrote:
>
>>       ;; `^string1^string2^'
>>       ;;      Quick Substitution.  Repeat the last command, replacing
>>       ;;      STRING1 with STRING2.  Equivalent to `!!:s/string1/string2/'
>
> That substitution is only supposed to be performed when occuring at the
> start of the line.

Hmm, I see that's the case by experimenting with bash, although the bash
manual doesn't seem to actually say that.