On Fri, Oct 21, 2005 at 01:42:05AM +0300, Alexander Gattin wrote: > On Wed, Oct 19, 2005 at 05:36:29PM -0700, Steve Langasek wrote: > > > Yes, I see this (pre-0.80 version): > > > 1. fprintf(stderr, "%s", prompt); > > > 2. tcsetattr(STDIN_FILENO, TCSAFLUSH, ...); > > > 3. read(STDIN_FILENO, ...); > > > 4. tcsetattr(STDIN_FILENO, TCSADRAIN, ...);
> > > OK. Even having 2, 1, 3, 4 sequence now, don't you > > > think it's useful to have fflush(stderr) immediately > > > after fprintf(stderr, ...)? > > Sorry, what problem are you trying to solve? > Excuse me for the confusion. I talk her about another > issue, similar to what we have in bug #333138. > Now I tend to agree with Robert that this is a bug, > because fact of stdin being or not being tty should not > affect buffering/flushing of stdout/stderr. At least > this behaviour is rather strange and unexpected to > majority of *nix users, admins and programmers. It's not unusual for password-related tools to insist on a tty; though granted, misc_conv allows non-tty conversations, so this is still a bug, just not one I'd consider very serious. Anyway, if you can send me a patch, I'll see about getting a fix pushed upstream. Thanks, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/
signature.asc
Description: Digital signature
