Michelle Konzack wrote:
Am 2008-03-05 13:10:37, schrieb Bob McGowan:
Mark Clarkson wrote:
On Wed, 05 Mar 2008 12:16:02 -0800
Bob McGowan <[EMAIL PROTECTED]> wrote:
Brian wrote:
So can you explain exactly what the first < <( echo "$teststring" )
does exactly please?
man bash
8<
Michelle Konzack wrote:
Am 2008-03-05 14:13:33, schrieb Brian:
teststring="one two three four five six"
{ read A B C D E F; } < <( echo "$teststring" )
echo "Data received = $E Bytes"
END OF REPLIED MESSAGE
This look a little bit weird. Why n
Am 2008-03-05 13:10:37, schrieb Bob McGowan:
> Mark Clarkson wrote:
> >On Wed, 05 Mar 2008 12:16:02 -0800
> >Bob McGowan <[EMAIL PROTECTED]> wrote:
> >
> >>Brian wrote:
> >>>So can you explain exactly what the first < <( echo "$teststring" )
> >>>does exactly please?
man bash
8<--
Am 2008-03-05 14:13:33, schrieb Brian:
> teststring="one two three four five six"
> { read A B C D E F; } < <( echo "$teststring" )
> echo "Data received = $E Bytes"
END OF REPLIED MESSAGE
This look a little bit weird. Why not use:
8<--
On Wed March 5 2008 15:36:50 William Pursell wrote:
> As far as I can tell, the following 4 commands should
> all behave the same, but the last one hangs. Can anyone
> see why?
>
> $ cat <(echo foo)
> foo
> $ bash -c 'cat <(echo foo)'
> foo
> $ echo foo | bash -c 'cat'
> foo
> $ bash -c 'cat' <(ec
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
William Pursell wrote:
> I couldn't find the correct place to interject this question in
> the thread, so I fairly randomly selected this location...
>
> As far as I can tell, the following 4 commands should
> all behave the same, but the last one han
Mark Clarkson wrote:
On Wed, 05 Mar 2008 13:10:37 -0800
Bob McGowan <[EMAIL PROTECTED]> wrote:
If I do the "process substitution" using a stand alone programs, it
works as described:
$ wc <(echo this is a test)
1 4 15 /dev/fd/63
I couldn't find the correct place to
Mark Clarkson wrote:
On Wed, 05 Mar 2008 13:10:37 -0800
Bob McGowan <[EMAIL PROTECTED]> wrote:
Mark Clarkson wrote:
On Wed, 05 Mar 2008 12:16:02 -0800
Bob McGowan <[EMAIL PROTECTED]> wrote:
Brian wrote:
So can you explain exactly what the first < <( echo
"$teststring" ) does exactly please?
On Wed, 05 Mar 2008 13:10:37 -0800
Bob McGowan <[EMAIL PROTECTED]> wrote:
> Mark Clarkson wrote:
> > On Wed, 05 Mar 2008 12:16:02 -0800
> > Bob McGowan <[EMAIL PROTECTED]> wrote:
> >
> >> Brian wrote:
> >>> So can you explain exactly what the first < <( echo
> >>> "$teststring" ) does exactly ple
Mark Clarkson wrote:
On Wed, 05 Mar 2008 12:16:02 -0800
Bob McGowan <[EMAIL PROTECTED]> wrote:
Brian wrote:
So can you explain exactly what the first < <( echo "$teststring" )
does exactly please?
In any case, I'd be interested in knowing where you found this
construct.
The bash man page
On Wed, 05 Mar 2008 12:16:02 -0800
Bob McGowan <[EMAIL PROTECTED]> wrote:
> Brian wrote:
> >
> > So can you explain exactly what the first < <( echo "$teststring" )
> > does exactly please?
> >
> In any case, I'd be interested in knowing where you found this
> construct.
>
The bash man page s
Brian wrote:
Mark Clarkson wrote:
On Tue, 04 Mar 2008 18:46:05 +0100
Brian <[EMAIL PROTECTED]> wrote:
I could not get this to work, the shell complains:
./dirvish-mail.sh: 98: Syntax error: redirection unexpected
Interesting to note that this does not work under busybox. I think
this is ra
Mark Clarkson wrote:
On Tue, 04 Mar 2008 18:46:05 +0100
Brian <[EMAIL PROTECTED]> wrote:
I could not get this to work, the shell complains:
./dirvish-mail.sh: 98: Syntax error: redirection unexpected
Interesting to note that this does not work under busybox. I think
this is rather an esoter
On Tue, 04 Mar 2008 18:46:05 +0100
Brian <[EMAIL PROTECTED]> wrote:
>
> I could not get this to work, the shell complains:
>
> ./dirvish-mail.sh: 98: Syntax error: redirection unexpected
>
Interesting to note that this does not work under busybox. I think
this is rather an esoteric but often u
Mark Clarkson wrote:
On Mon, 2008-03-03 at 19:48 +0100, Brian wrote:
echo "$teststring" | { read A B C D E F; }
echo "Data received = $E Bytes" <--- $E is empty
{ read A B C D E F; } < <( echo "$teststring" )
echo "Data received = $E Bytes" <--- $E is empty
Robomod,
I could not get this
Georg Neis wrote:
Brian wrote:
The following does not (the value is empty):
echo "$teststring" | { read A B C D E F; }
echo "Data received = $E Bytes" <--- $E is empty
I assume it has something to do with the read command being executed in
a subshell.
Yes.
So how can I extract the parts
Brian wrote:
> The following does not (the value is empty):
>
> echo "$teststring" | { read A B C D E F; }
> echo "Data received = $E Bytes" <--- $E is empty
>
> I assume it has something to do with the read command being executed in
> a subshell.
Yes.
> So how can I extract the parts I want
On Mon, 2008-03-03 at 19:48 +0100, Brian wrote:
> echo "$teststring" | { read A B C D E F; }
> echo "Data received = $E Bytes" <--- $E is empty
{ read A B C D E F; } < <( echo "$teststring" )
echo "Data received = $E Bytes" <--- $E is empty
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with
On Mon, Mar 03, 2008 at 07:48:49PM +0100, Brian wrote:
> Hi,
>
> I tried using bash to split a string. This works OK:
>
> echo "$teststring" | { read A B C D E F; echo "Data received = $E Bytes"; }
>
> The following does not (the value is empty):
>
> echo "$teststring" | { read A B C D E F; }
> ec
Hi,
I tried using bash to split a string. This works OK:
echo "$teststring" | { read A B C D E F; echo "Data received = $E Bytes"; }
The following does not (the value is empty):
echo "$teststring" | { read A B C D E F; }
echo "Data received = $E Bytes" <--- $E is empty
I assume it has somet
20 matches
Mail list logo
