zsh-users
 help / color / mirror / code / Atom feed
From: Vincent Lefevre <vincent@vinc17.org>
To: zsh-users@sunsite.dk
Subject: |& loses data (buffering bug?)
Date: Fri, 13 Feb 2004 15:15:05 +0100	[thread overview]
Message-ID: <20040213141505.GG27168@greux.loria.fr> (raw)

Hi,

I've noticed that when I use |&, data from either stdout or stderr
(of the first command) are lost. For instance, the output of a
"cvs status |& less" sometimes gives the following:

[...]
===================================================================
File: zeta.c            Status: Up-to-date

   Working revision:    1.37
   Repository revision: 1.37    /CVS/spaces/mpfr/zeta.c,v
   Sticky Tag:          (none)
   Sticky Date:         (none)
   Sticky Options:      (none)

cvs status: Examining o.alpha
cvs status: Examining o.linux
cvs status: Examining o.solaris
cvs status: Examining o.sunos
cvs status: Examining tests

   Sticky Options:      (none)

===================================================================
File: tagm.c            Status: Up-to-date
[...]

Contents from stdout have been lost here. The problem occurs either
with less or with grep; for instance, a "cvs status |& grep Status"
gave:

[...]
File: replace_all       Status: Up-to-date
File: rint.c            Status: Up-to-date
File: round_prec.c      Status: Up-t
File: set_str.c         Status: Up-to-date
File: set_str_raw.c     Status: Up-to-date
[...]

instead of:

[...]
File: replace_all       Status: Up-to-date
File: rint.c            Status: Up-to-date
File: round_prec.c      Status: Up-to-date
File: round_raw_generic.c       Status: Up-to-date
File: save_expo.c       Status: Up-to-date
File: set.c             Status: Up-to-date
File: set_d.c           Status: Up-to-date
File: set_dfl_prec.c    Status: Up-to-date
File: set_exp.c         Status: Up-to-date
File: set_f.c           Status: Up-to-date
File: set_inf.c         Status: Up-to-date
File: set_ld.c          Status: Up-to-date
File: set_nan.c         Status: Up-to-date
File: set_prc_raw.c     Status: Up-to-date
File: set_prec.c        Status: Up-to-date
File: set_q.c           Status: Up-to-date
File: set_rnd.c         Status: Up-to-date
File: set_si.c          Status: Up-to-date
File: set_str.c         Status: Up-to-date
File: set_str_raw.c     Status: Up-to-date
[...]

When I redirect the output of the second command to a file, it seems
that the problem never occurs.

Is it a bug from zsh (I'm using zsh 4.0.9) or from cvs?

-- 
Vincent Lefèvre <vincent@vinc17.org> - Web: <http://www.vinc17.org/> - 100%
validated (X)HTML - Acorn Risc PC, Yellow Pig 17, Championnat International
des Jeux Mathématiques et Logiques, TETRHEX, etc.
Work: CR INRIA - computer arithmetic / SPACES project at LORIA


             reply	other threads:[~2004-02-13 14:15 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-13 14:15 Vincent Lefevre [this message]
2004-02-13 14:33 ` Peter Stephenson
2004-02-13 14:43   ` Vincent Lefevre
2004-02-13 15:00     ` Peter Stephenson
2004-02-13 15:30       ` Vincent Lefevre
2004-02-13 15:44         ` Vincent Lefevre
2004-02-13 16:12           ` Peter Stephenson
2004-02-13 16:17             ` Vincent Lefevre
2004-02-13 17:33 ` Vincent
2004-02-14 11:32   ` Vincent Lefevre

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20040213141505.GG27168@greux.loria.fr \
    --to=vincent@vinc17.org \
    --cc=zsh-users@sunsite.dk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).