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
Chet Ramey wrote:
> On 6/23/18 3:44 PM, L A Walsh wrote:
> > Seems like the original missed being sent toe the bug-bash alias.
>
> It was not posted to bug-bash.
For bug-bash was in the hold queue for human moderation. Although it
seems off topic for this mailing list it has already had three re
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_64-pc-linux-gnu'
-DCONF_VENDOR='pc' -DLOCALEDIR='/usr/sh
On 6/23/18 3:44 PM, L A Walsh wrote:
>
> What's the context for this? FWIW, removing non-bug-bash-subscribers
> (that I know of), as my question is aimed, I guess, at Eduardo,
> but not sure if it was posted to bash list or not?
It was not posted to bug-bash.
--
``The lyf so short, the craft s
Seems like the original missed being sent toe the bug-bash alias.
But I'm curious...
What's the context for this? FWIW, removing non-bug-bash-subscribers
(that I know of), as my question is aimed, I guess, at Eduardo,
but not sure if it was posted to bash list or not?
Maybe I just missed it?
T
On Sat, Jun 23, 2018 at 12:08 PM, pg wrote:
[...]
> Description: BASHJ - ANNOUNCE TO THE DEVELOPMENT TEAM OF BASH
>
> I am pleased to inform you about bashj - a bash 'mutant' with java
> support.
> This product opens numerous very interesting fields to bash developers.
I have a few questi
