Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > gnu.bash.bug > #14122 > unrolled thread

Re: Redirect to variable

Back to article view | Back to gnu.bash.bug

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: Redirect to variable Chet Ramey <chet.ramey@case.edu> - 2018-05-21 10:12 -0400

#14122 — Re: Redirect to variable

On 5/20/18 10:21 PM, PePa wrote:
> 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 this idea here, but didn't get any reply, maybe this
> isn't the right place? Am I blacklisted??

It's not possible, in general, to open a file descriptor to an arbitrary
block of memory, especially given file descriptor inheritance between
processes.

What you're asking for is syntactic sugar for:

some-command > temp-file
echo '#' >> temp-file
variablename=$(< temp-file)
rm -f temp-file
variablename=${variablename%?}

I would look at a sample implementation, possibly using mmap, if someone
did one.

Chet
-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer
		 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU    chet@case.edu    http://tiswww.cwru.edu/~chet/

[toc] | [standalone]

Back to top | Article view | gnu.bash.bug

csiph-web