mwoehlke <[EMAIL PROTECTED]> wrote:
> I am trying to figure out how to run a command and pipe the output
> through tee, and then check the status of the original command.
This uses a bash-specific feature:
cmd > >(tee file); status=$?
This should work on any sh:
exec 3>&1 && status=`exec 4>&1 &&
Not really a bug, but this seems to be the only bash list gname knows
about, so...
I am trying to figure out how to run a command and pipe the output
through tee, and then check the status of the original command. Normally
I am a very competent shell programmer, but this one has me stumped!
On Tue, Sep 26, 2006 at 11:45:42AM -0400, Paul Jarc wrote:
> mwoehlke <[EMAIL PROTECTED]> wrote:
> > I am trying to figure out how to run a command and pipe the output
> > through tee, and then check the status of the original command.
>
> This uses a bash-specific feature:
> cmd > >(tee file); s
Paul Jarc wrote:
mwoehlke <[EMAIL PROTECTED]> wrote:
I am trying to figure out how to run a command and pipe the output
through tee, and then check the status of the original command.
This uses a bash-specific feature:
cmd > >(tee file); status=$?
Thanks Paul and Stephen for the replies. I a
Vasily Tarasov wrote:
> I suppose I've found a bug;
I need to make this part of the FAQ. The `:' is special to readline: it
splits words for the word completion code.
The default set of such characters is available in the COMP_WORDBREAKS
variable. Removing `:' from the value of that variable
Chet Ramey <[EMAIL PROTECTED]> wrote:
> Vasily Tarasov wrote:
>
>> I suppose I've found a bug;
>
> I need to make this part of the FAQ. The `:' is special to readline: it
> splits words for the word completion code.
That explains some of what's going on in this case, but not all. For
the first
> Chet Ramey <[EMAIL PROTECTED]> wrote:
> > Vasily Tarasov wrote:
> >
> >> I suppose I've found a bug;
> >
> > I need to make this part of the FAQ. The `:' is special to readline: it
> > splits words for the word completion code.
>
> That explains some of what's going on in this case, but not al
Chet Ramey <[EMAIL PROTECTED]> wrote:
>> Chet Ramey <[EMAIL PROTECTED]> wrote:
>> Also, after two tabs, we have "qwe:qwe:o", but further tabs don't add
>> any more "qwe:"'s for some reason I don't understand.
>
> Because the colon is still a word break character, and readline passes `o'
> to the co
> So it looks like the entire word is passed to the completion function;
> COMP_WORDBREAKS is not consulted at that point. COMP_WORDBREAKS is
> only used to decide how much text to erase before inserting the
> completion text. Is that intended? Is the completion function
> supposed to take care
Configuration Information [Automatically generated, do
not change]:
Machine: i386
OS: linux-gnu
Compiler: i386-pc-linux-gnu-gcc
Compilation CFLAGS: -DPROGRAM='bash'
-DCONF_HOSTTYPE='i386' -DCONF_OSTYPE='linux-gnu'
-DCONF_MACHTYPE='i386-pc-linux-gnu' -DCONF_VENDOR='pc'
-DLOCALEDIR='/usr/share/local
Configuration Information [Automatically generated, do
not change]:
Machine: i386
OS: linux-gnu
Compiler: i386-pc-linux-gnu-gcc
Compilation CFLAGS: -DPROGRAM='bash'
-DCONF_HOSTTYPE='i386' -DCONF_OSTYPE='linux-gnu'
-DCONF_MACHTYPE='i386-pc-linux-gnu' -DCONF_VENDOR='pc'
-DLOCALEDIR='/usr/share/local
Lorenzo Viali <[EMAIL PROTECTED]> wrote:
> eval "\"$CMDFILE\" $list"
> because i need $CMDFILE to receive more than
> one argument; but what happens is that if in the
> script's option's arguments, there are substrings like
> $i, those variable are expanded
That will also happen wi
12 matches
Mail list logo
