|& broken in 4.0.1-pre-3?

|& broken in 4.0.1-pre-3?

[Thomas Köhler]

[-- Attachment #1: Type: text/plain, Size: 831 bytes --]

Hi,

~> zsh -f
picard% vim --version 2>/dev/null

picard% vim --version >/dev/null
VIM - Vi IMproved 6.0ad ALPHA (2001 Apr 29, compiled Apr 30 2001 19:18:20)
Compiled by jean-luc@picard
[Rest of output snipped, you get the idea]
picard% vim --version 2>&1 | head

picard% vim --version |& head

picard% echo $ZSH_VERSION
4.0.1-pre-3
picard% uname -a
Linux picard 2.2.17 #7 Sat Jan 27 09:58:58 CET 2001 i686 unknown

Something is broken here, isn't it? stderr is being ignored instead of
being redirected...

CU,
Thomas

-- 
 Thomas Köhler Email:   jean-luc@picard.franken.de     | LCARS - Linux
     <><        WWW:     http://jeanluc-picard.de      | for Computers
                IRC:             jeanluc               | on All Real
               PGP public key available from Homepage! | Starships

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

Re: |& broken in 4.0.1-pre-3?

[Bart Schaefer]

On Apr 30,  9:24pm, Thomas Ko%hler wrote:
> Subject: |& broken in 4.0.1-pre-3?
> 
> picard% vim --version |& head
> 
> picard% echo $ZSH_VERSION
> 4.0.1-pre-3
> picard% uname -a
> Linux picard 2.2.17 #7 Sat Jan 27 09:58:58 CET 2001 i686 unknown

I suspect it's a VIM thing -- can you reproduce it with some other command?

aztec% uname -a
Linux aztec.zanshin.com 2.2.19-6.2.1 #1 Mon Apr 9 22:52:58 EDT 2001 i686 unknown
aztec% echo $ZSH_VERSION
4.0.1-pre-3
aztec% vim --version |& head
VIM - Vi IMproved 5.7 (2000 Jun 24, compiled Jan 31 2001 06:10:12)
Included patches: 1-8, 12-24
Compiled by prospector@porky.devel.redhat.com, with (+) or without (-):
+autocmd -browse ++builtin_terms +byte_offset +cindent +cmdline_compl 
+cmdline_info +comments +cryptv +cscope +dialog_con +digraphs +emacs_tags +eval 
+ex_extra +extra_search +farsi +file_in_path -osfiletype +find_in_path +fork() 
-GUI -hangul_input +insert_expand +langmap +linebreak +lispindent +menu 
+mksession +modify_fname +mouse +mouse_dec +mouse_gpm +mouse_netterm 
+mouse_xterm +multi_byte +perl +python +quickfix +rightleft +scrollbind 
+smartindent -sniff +statusline +syntax +tag_binary +tag_old_static 

Re: [14172] |& broken in 4.0.1-pre-3?

[Danek Duvall]

I haven't actually looked to see what changes Bram put into 6.0ad, but he
was talking about determining if vim was attached to a terminal by checking
to see if stderr was attached to the terminal.

Each case here where the output is missing you've sent stderr somewhere
other than the terminal, and so vim figures it can't print.

There really ought to be a better way to get this information -- all three
standard fds can be redirected, but the program can still be running in a
terminal, no?

Danek

Re: |& broken in 4.0.1-pre-3?

[Thomas Köhler]

[-- Attachment #1: Type: text/plain, Size: 1025 bytes --]

On Mon, Apr 30, 2001 at 03:24:08PM -0700,
Bart Schaefer <schaefer@candle.brasslantern.com> wrote:
> On Apr 30,  9:24pm, Thomas Ko%hler wrote:
> > Subject: |& broken in 4.0.1-pre-3?
> > 
> > picard% vim --version |& head
> > 
> > picard% echo $ZSH_VERSION
> > 4.0.1-pre-3
> > picard% uname -a
> > Linux picard 2.2.17 #7 Sat Jan 27 09:58:58 CET 2001 i686 unknown
> 
> I suspect it's a VIM thing -- can you reproduce it with some other command?

Uhm, right, vim is at fault. Oh well, so I've sent the bugreport to the
wrong mailing list ;-)

> aztec% vim --version |& head
> VIM - Vi IMproved 5.7 (2000 Jun 24, compiled Jan 31 2001 06:10:12)

That old vim-5.7 floating around here works fine, too :-)

Ciao,
Thomas

-- 
 Thomas Köhler Email:   jean-luc@picard.franken.de     | LCARS - Linux
     <><        WWW:     http://jeanluc-picard.de      | for Computers
                IRC:             jeanluc               | on All Real
               PGP public key available from Homepage! | Starships

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

Re: [14172] |& broken in 4.0.1-pre-3?

[Thomas Köhler]

[-- Attachment #1: Type: text/plain, Size: 1334 bytes --]

On Mon, Apr 30, 2001 at 03:58:20PM -0700,
Danek Duvall <duvall@emufarm.org> wrote:
> 
> I haven't actually looked to see what changes Bram put into 6.0ad, but he
> was talking about determining if vim was attached to a terminal by checking
> to see if stderr was attached to the terminal.

Direct hit :)

> Each case here where the output is missing you've sent stderr somewhere
> other than the terminal, and so vim figures it can't print.

Bad luck that this is the wrong way to figure that out ;)

> There really ought to be a better way to get this information -- all three
> standard fds can be redirected, but the program can still be running in a
> terminal, no?

Yes.

But another question:
How do I redirect some fds and still get them to the screen?
With the multios option, I can do things like
foo >x >y >z | grep something
But how do I do
foo >x >y >z 
and still get stdout to stdout?
Of course, for stdout,
foo >x >y |tee z
works; but how do I get this to work for stderr?

> Danek

Ciao,
Thomas

-- 
 Thomas Köhler Email:   jean-luc@picard.franken.de     | LCARS - Linux
     <><        WWW:     http://jeanluc-picard.de      | for Computers
                IRC:             jeanluc               | on All Real
               PGP public key available from Homepage! | Starships

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

Re: [14172] |& broken in 4.0.1-pre-3?

[Bart Schaefer]

On May 1,  9:44am, Thomas Köhler wrote:
}
} But another question:
} How do I redirect some fds and still get them to the screen?

Assuming we're not talking about vim, you do it by redirecting the descriptor
to itself, like this:

zsh% foo >&1 >x >y >z

Remember, though, that multios are processed by what amounts to a background
`tee' job, so `foo' may finish and give you back a prompt before all the
output has actually appeared on your terminal.

} Of course, for stdout,
} foo >x >y |tee z
} works; but how do I get this to work for stderr?

Same basic idea:

zsh% foo 2>&1 2>x 2>y 2>z

Note that 2>& with a file name rather than a following digit will open the
file twice, giving you two copies of stderr in that file.  I'm not sure
that's supposed to happen ...

-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com

Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net   

Re: [14172] |& broken in 4.0.1-pre-3?

[Thomas Köhler]

On Tue, May 01, 2001 at 08:49:59AM +0000,
Bart Schaefer <schaefer@candle.brasslantern.com> wrote:
> 
> On May 1,  9:44am, Thomas Köhler wrote:
> }
> } But another question:
> } How do I redirect some fds and still get them to the screen?
> 
> Assuming we're not talking about vim, you do it by redirecting the descriptor
> to itself, like this:
> 
> zsh% foo >&1 >x >y >z

Uhm, that's the trick. Fine :-)

> Remember, though, that multios are processed by what amounts to a background
> `tee' job, so `foo' may finish and give you back a prompt before all the
> output has actually appeared on your terminal.

Not too much of an issue.

> } Of course, for stdout,
> } foo >x >y |tee z
> } works; but how do I get this to work for stderr?
> 
> Same basic idea:
> 
> zsh% foo 2>&1 2>x 2>y 2>z

Well... better yet,
foo 2>&2 2>x 2>y 2>z
works :-)

> Note that 2>& with a file name rather than a following digit will open the
> file twice, giving you two copies of stderr in that file.  I'm not sure
> that's supposed to happen ...

Well, I try to avoid that anyways :-)

Ciao,
Thomas

-- 
Thomas Köhler             Linux without limits: http://linux.s390.org/
Millenux GmbH      http://www.millenux.de/  thomas.koehler@millenux.de
Lilienthalstraße 2                            phone: +49.711.88770.300
D-70825 Stuttgart-Korntal                       fax: +49.711.88770.349