overloading the redirect operators)
> I think I'm starting to see the value in it. I can't promise
> anything at this point but I'd like to see what I can come
> up with.
> - Original Message -
> From: chet.ra...@case.edu
> To:"Peter Passchier"
't promise
anything at this point but I'd like to see what I can come
up with.
- Original Message -
From: chet.ra...@case.edu
To:"Peter Passchier" , "Martijn Dekker"
,
Cc:
Sent:Mon, 25 Jun 2018 09:11:45 -0400
Subject:Re: Directing into a variable doesn't wor
Martijn Dekker wrote:
Op 24-06-18 om 05:08 schreef Peter Passchier:
With memory being abundant and filesystem access expensive, I want to
put stdout and stderr of a command into variables (without needing to
write to a file):
output=$($command 2>>>errors)
This would not work even i
On 06/25/2018 08:11 PM, Chet Ramey wrote:
> The answer is ultimately the same as it was last month:
>
> http://lists.gnu.org/archive/html/bug-bash/2018-05/msg00056.html
Oh wow, you replied..! I never got this in my inbox somehow...
I guess it is syntactic sugar (although Greg's post shows it isn
On 6/24/18 11:26 AM, Peter Passchier wrote:
> Thank you for the feedback, very insightful. Yes, scratch that first
> 'example'. Yay for the here-variable redirection!
The answer is ultimately the same as it was last month:
http://lists.gnu.org/archive/html/bug-bash/2018-05/msg00056.html
--
``Th
On Sun, Jun 24, 2018 at 8:35 PM, Peter Passchier
wrote:
> On 06/25/2018 12:27 AM, Robert Elz wrote:
> > That's not the real issue - rather it is that a here doc is presented to
> the
> > command beng run as a file descrptior
>
> OK, thanks, that makes sense. In the case of a here-variable, that w
On 06/25/2018 12:27 AM, Robert Elz wrote:
> That's not the real issue - rather it is that a here doc is presented to the
> command beng run as a file descrptior
OK, thanks, that makes sense. In the case of a here-variable, that would
definitely be the case then.
Peter
Date:Sun, 24 Jun 2018 22:26:52 +0700
From:Peter Passchier
Message-ID:
| I am surprised by the general internal usage of temporary files for
| here-documents & here-strings, because (generally speaking) memory is
| quite abundant,
That's not the real issue - ra
Thank you for the feedback, very insightful. Yes, scratch that first
'example'. Yay for the here-variable redirection!
I am surprised by the general internal usage of temporary files for
here-documents & here-strings, because (generally speaking) memory is
quite abundant, and here-strings and even
Op 24-06-18 om 05:08 schreef Peter Passchier:
With memory being abundant and filesystem access expensive, I want to
put stdout and stderr of a command into variables (without needing to
write to a file):
output=$($command 2>>>errors)
This would not work even if the feature is implemented. The
With memory being abundant and filesystem access expensive, I want to
put stdout and stderr of a command into variables (without needing to
write to a file):
output=$($command 2>>>errors)
Or:
$command >>>output 2>>>errors
Obviously this gives a syntax error now, as this intuitive idea isn't
i
11 matches
Mail list logo
