From: Richard Coleman <coleman@math.gatech.edu>
To: Wolfgang Hukriede <whukriede@ifm.uni-kiel.de>
Cc: zsh-workers@math.gatech.edu
Subject: Re: zsh-3.0.2 repacked
Date: Thu, 19 Dec 1996 20:22:33 -0500 [thread overview]
Message-ID: <199612200122.UAA02421@redwood.skiles.gatech.edu> (raw)
In-Reply-To: Your message of "Fri, 20 Dec 1996 01:38:39 +0100." <199612200038.BAA18599@sally.ifm.uni-kiel.de>
> I'm sorry, but definitely there's no such alleged bug in the NeXTStep libc.
> Setting BAUD to zero fixes the jumping movement of the cursor, nothing else,
> the screen output is as fast/slow as without setting BAUD.
>
> Then, after:
>
> setvbuf(shout, NULL, _IOFBF, 0);
>
> shout->_bufsiz gives ZERO, as well as shout->_base still is ZERO, in other
> words, shout is unbuffered. I cannot imagine this should be different with
> other libc's. Have you actually checked this?
>
> Also, to fix that all,
>
> setvbuf(shout, NULL, _IOFBF, BUFSIZ);
>
> is totally sufficient, and has the advantage, that the buffer only is
> allocated if shout is actually used. (Further: imo there's really no need for
> conditional compilation here.).
This is definitely a bug. If second argument is NULL, and the mode is
either _IOFBF (fully buffered) or _IOLBF (line buffered), then the libc
should ignore the fourth argument and allocate a buffer of the appropriate
length. This is according to Steven's "Advanced Programming in the Unix
Environment".
rc
next prev parent reply other threads:[~1996-12-20 1:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-12-20 0:38 Wolfgang Hukriede
1996-12-20 0:55 ` Zoltan Hidvegi
1996-12-20 1:22 ` Richard Coleman [this message]
1996-12-20 1:16 Wolfgang Hukriede
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=199612200122.UAA02421@redwood.skiles.gatech.edu \
--to=coleman@math.gatech.edu \
--cc=whukriede@ifm.uni-kiel.de \
--cc=zsh-workers@math.gatech.edu \
/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).