[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Echoing commands
From: |
Greg Wooledge |
Subject: |
Re: Echoing commands |
Date: |
Thu, 13 Jun 2024 13:29:44 -0400 |
On Thu, Jun 13, 2024 at 11:51:13AM -0400, Dale R. Worley wrote:
> For instance, how should this be logged?
>
> $ { echo foo ; echo bar ; } >/dev/null
> + echo foo
> + echo bar
I'm 99% sure I know what answer the OP of this thread will give:
"It should write '{ echo foo ; echo bar ; } >/dev/null', nothing
more and nothing less."
What they want is for the shell to keep track of the actual lines of
code that were read and parsed, and whenever a command is executed in
the future, look up the original line of the script and write that,
without any expansions.
I've seen this same request from several people over the years.
I have no idea how much work it would be to implement, and no idea what
kind of benefits the OP envisions this will give them.
- Re: Echoing commands, (continued)
Re: Echoing commands, Koichi Murase, 2024/06/12
Re: Echoing commands, Robert Elz, 2024/06/13