Chet Ramey wrote:
> Bob Proulx wrote:
> > That is one of the reasons I don't like the /dev/std{err,in,out}
> > things. They are not portable. They do different things on different
> > systems. I avoid them.
>
> I've considered emulating it everywhere, regardless of what the OS
> provides, but I
On 9/16/14, 3:00 PM, Bob Proulx wrote:
> That is one of the reasons I don't like the /dev/std{err,in,out}
> things. They are not portable. They do different things on different
> systems. I avoid them.
I've considered emulating it everywhere, regardless of what the OS
provides, but I'd get jus
On Tue, Sep 16, 2014 at 2:03 AM, Ralf Goertz wrote:
> Am Sat, 13 Sep 2014 12:53:48 -0600
> schrieb Bob Proulx :
>
>
> > Dennis Williamson wrote:
> > > Bob Proulx wrote:
> > > > { for i in file[12] ; do cat "$i" ; done ;} > both
>
> > > There's no need for the curly braces and the last semicolon
Greg Wooledge wrote:
> It's important to note that the following two cases are *not*
> equivalent:
>
>cat "$i" >/dev/stdout
>program -i "$i" -o /dev/stdout
>
> In the first case, the /dev/stdout is part of a redirection. On
> platforms that do not have a native /dev/stdout in the file sy
On 9/16/14, 2:47 AM, Martin Bruchanov wrote:
> Hello,
>
>
> I've found this bug, when changed an string variable to hash, but left the
> following code for test of zero code. It happens just inside function. I'm
> using 4.1.2(1)-release,
Thanks for the report. This was fixed around four year
On Tue, Sep 16, 2014 at 09:03:20AM +0200, Ralf Goertz wrote:
> Actually things are more complicated. I do need the /dev/stdout part. I
> obiously don't have the problem with `cat' but with some other program
> $ for i in file[12] ; do program -i "$i" -o /dev/stdout ; done > outfile
It's important
Hello,
I've found this bug, when changed an string variable to hash, but left the
following code for test of zero code. It happens just inside function. I'm
using 4.1.2(1)-release,
BASH=/bin/bash
BASHOPTS=checkwinsize:cmdhist:expand_aliases:extquote:force_fignore:hostcomplete:interactive_co
Ralf Goertz wrote:
> Actually things are more complicated. I do need the /dev/stdout part. I
> obiously don't have the problem with `cat' but with some other program
> that doesn't write to stdout per se and expects a -o parameter for the
> output file. And this program just accepts one input file.
Am Sat, 13 Sep 2014 12:53:48 -0600
schrieb Bob Proulx :
> Dennis Williamson wrote:
> > Bob Proulx wrote:
> > > { for i in file[12] ; do cat "$i" ; done ;} > both
> > There's no need for the curly braces and the last semicolon.
>
> Of course you are totally right. I was distracted by the subs
