Date:	Wed, 16 May 2001 18:36:23 +0300 (IDT)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	Michiel de Bondt <michielb AT sci DOT kun DOT nl>
cc:	djgpp AT delorie DOT com
Subject:	Re: how to flush cprintf output
In-Reply-To:	<3B028BE8.3BB100AD@sci.kun.nl>
Message-ID:	<Pine.SUN.3.91.1010516183216.919A-100000@is>
MIME-Version:	1.0
Reply-To:	djgpp AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Wed, 16 May 2001, Michiel de Bondt wrote:

> Hans-Bernhard Broeker wrote:
> 
> > There is none --- cprintf() isn't buffered, so it doesn't need any
> > fflush workalike, to begin with. Instead, you'ld have to be sure you
> > fflush(stdout) before any cprintf() or gotoxy() call following a
> > printf().
> 
> This does not agree with observation. Probably, Windows 95 should be
> blamed.

Please describe what do you see that contradicts what Hans-Bernhard 
wrote.  AFAIK, Windows 9X does not change the effect of cprintf in any 
way.

> I wish to print all information to stdout, except the progress asterisks
> "*" and search paths, and the "\b \b" to remove them.

And what do you want to do with progress indicator and search path?  IN 
particular, what do you want to do with them if stdout is redirected?

> The program dvips distinguishes console output and
> standard output as well, i.e. it seems so at least. How can that be?

Perhaps because it prints part of the text to stderr and the rest to 
stdout.

- Raw text -