...

...

following trivial observation i made (several runs)[...] Has anybody similar statistics?

Just another trivial observation, that in dosish os displaying is even more expensive.

hm, not in a windows shell; it depends on the font you use!

well, yes, it depends on the font, but even for the simplest raster font the windowish terminal (cmd, not custom shell I use) still seems to be slower. but ok, i thought it is obvious, if not, further tests are to be done. -- Pawe/l Jackowski P.Jackowski@gust.org.pl

...

...

...

...

"Martin" == Martin Schröder writes:

On 2005-12-22 10:39:06 +0100, Hans Hagen wrote:

...

are chars written one by one or by line? maybe there is some intermediate way possible:

- normal messages -> buffered - immediate/write16 -> flush pending messages and write unbuffered

And what about [1][2]? I want to see the time between [ and 1 and ] :-)

Yes, it is annoying if you see nothing for a long time and then a complete line appears. But do not expect to see anything at all when you buy a new computer today. On my new machine (AMD64, 2.2 GHz) texbook.tex compiles within 0.665 seconds. That's about 1.5 ms per page! What do you expect to see? It seems to be reasonable to give up the feature you asked for and try to get a result as fast as possible. There is one big problem though: What happens when TeX runs into an endless loop? You don't see where it happens if only complete lines are issued. Regards, Reinhard -- ---------------------------------------------------------------------------- Reinhard Kotucha Phone: +49-511-4592165 Marschnerstr. 25 D-30167 Hannover mailto:reinhard.kotucha@web.de ---------------------------------------------------------------------------- Microsoft isn't the answer. Microsoft is the question, and the answer is NO. ----------------------------------------------------------------------------

...

...

...

...

"Hartmut" == Hartmut Henkel writes:

On Fri, 23 Dec 2005, Reinhard Kotucha wrote:

...

There is one big problem though: What happens when TeX runs into an endless loop? You don't see where it happens if only complete lines are issued.

this can be handled by a reasonable timeout, using function select().

A timeout is not a solution. TeX simply doesn't know what I want. Reinhard -- ---------------------------------------------------------------------------- Reinhard Kotucha Phone: +49-511-4592165 Marschnerstr. 25 D-30167 Hannover mailto:reinhard.kotucha@web.de ---------------------------------------------------------------------------- Microsoft isn't the answer. Microsoft is the question, and the answer is NO. ----------------------------------------------------------------------------