[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: greater-than + number sign = newlines in history

From: Robert Elz
Subject: Re: greater-than + number sign = newlines in history
Date: Mon, 04 May 2020 21:24:06 +0700

    Date:        Mon, 4 May 2020 08:58:08 -0400
    From:        Chet Ramey <address@hidden>
    Message-ID:  <address@hidden>

  | The command-oriented history mode has to pay attention to those,   ['#']
  | because shell comments are one place where you can't
  | replace a newline with a semicolon.

That makes sense.

  | It just needs to also pay attention to
  | the fact that bash is reading a here-document.

There is more to it than that.

If I do (type):

        while sleep 4
        echo abc#def

(where the indentation is just for the e-mail), what bash puts in
history is

        while sleep 4; do echo abc#def

(again indentation just for e-mail).   The # there is not a comment, and
if I quoted the arg to echo, I'd get

        while sleep 4; do echo "abc#def"; done

Only words starting with # need special treatment, not just any random '#'.
(The code is correctly executed, of course, and abc#def is printed every
4 secs.

However, while this one looks weird, it isn't actually incorrect,
unlike the here-doc one.

  | This was reported and fixed in October, 2019, and the fix is in the devel
  | branch.

That one probably deserves a patch.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]