I would like to do something like this, where output gets redirected
into a variable:
some-command >>> variablename1 2>>>variablename2
command-with-many-output-descriptors >>> var1 3>>> var3 4>>> var4
The idea is not needing files to be created but to just use memory. Half
a year ago I posted
On 5/18/18 7:06 AM, Luca Boccassi wrote:
> Network operating systems traditionally have provided a command
> line interface with "operation mode" and "configuration mode", with
> different auto-completion behaviour - specifically, with a small set
> of supported commands that are printed using the
On 5/18/18 5:34 AM, Luca Boccassi wrote:
> Currently writing history to syslog can be enabled at compile time by
> editing config-top.h and rebuilding.
> To allow more flexibility, and to allow users of distributions to
> enable this feature at runtime without having to rebuild bash, add a
>
On 2015-11-13 at 07:17, Greg Wooledge wrote:
> Actually in the most general case, where those output streams may
> contain NUL bytes, it requires two temp files, because you can't store
> arbitrary data streams in bash variables at all.
Why do bash variables use 0-terminated arrays instead of
