[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: "here strings" and tmpfiles
From: |
pepa65 |
Subject: |
Re: "here strings" and tmpfiles |
Date: |
Mon, 8 Apr 2019 23:36:39 -0700 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 |
On 8/4/2019 22:53, Robert Elz wrote:
> [Aside: when the destination is a builtin, another strategy is to
> simply write the here doc into mem, and have the builtin read directly
> from the mem buffer - no actual I/O of any kind involved at all.]
When in the past I proposed this syntax: cmd >>>var
the idea was to commit the output of a command into memory (in the form
of a variable), without requiring a pipe or file.
What is the technique you are referring to?
> | I think Linda's main drive is to seek improvement in how bash works.
>
> That's a fine objective - but remember that the shells primary purpose
> is to run other commands (interactively or via a script) - the real
> work should normally be done by the other commands, not by the shell.
But when data gets passed between commands, it would be great if memory
could be used for that, for various good reasons. :-)
Peter
- Re: "here strings" and tmpfiles, (continued)
Re: "here strings" and tmpfiles, L A Walsh, 2019/04/07
- Re: "here strings" and tmpfiles, Chet Ramey, 2019/04/08
- Re: "here strings" and tmpfiles, Robert Elz, 2019/04/09
- Re: "here strings" and tmpfiles,
pepa65 <=
- Re: "here strings" and tmpfiles, Robert Elz, 2019/04/09
- Re: "here strings" and tmpfiles, Greg Wooledge, 2019/04/09
- Re: "here strings" and tmpfiles, Chet Ramey, 2019/04/09
Re: "here strings" and tmpfiles, L A Walsh, 2019/04/09
Re: "here strings" and tmpfiles, Greg Wooledge, 2019/04/10
Re: "here strings" and tmpfiles, Greg Wooledge, 2019/04/10
Re: "here strings" and tmpfiles, Chet Ramey, 2019/04/10
Re: "here strings" and tmpfiles, konsolebox, 2019/04/10
Re: "here strings" and tmpfiles, Chet Ramey, 2019/04/10
Re: "here strings" and tmpfiles, konsolebox, 2019/04/10