🚀 go-pugleaf

In article <1992Jul31.021545.6738@sunb10.cs.uiuc.edu>, epstein@sparc9.cs.uiuc.edu (Milt Epstein) writes:

|> In <l7e56tINN880@utkcs2.cs.utk.edu> eijkhout@cupid.cs.utk.edu (Victor Eijkhout) writes:

|> >(For those of you who havent' heard of LT: it is a very fast -- assembler ! --
|> >implementation of TeX that continually reformats your input and displays
|> >this in the preview window. Every time you press a key, I think.)
|> 
|> Are there any problems caused when you are in the middle of typing in
|> some block of code, so at some points the file will not be complete,
|> correct tex/latex code, and if tex/latex is run then, you will get
|> errors (and the previewer may barf)?

Yes, you do get errors, and no, the previewer does not barf. Kudos to the
programmers at Blue Sky for this. All errors show up in a log window,
and I found this continuous string of error msgs somewhat disconcerting,
but then I clicked shut the log window, and it didn't bother me
anymore.

|> Currently, I use (Ed Reingold's) tex-mode in emacs, so while I'm
|> editing, I have xdvi running, and periodically run latex on the file
|> from within emacs (xdvi automatically looks at the new .dvi file).

Same idea, only not automatically performed.

|> I was thinking of writing some emacs code that automatically runs
|> latex on the file every so often (perhaps when it auto-saves).  The
|> above situation seemed like it would cause problems, though (e.g. if
|> when it runs latex, I am in the middle of entering a block, so I might
|> not have the appropriate \end or whatever, and latex -- and probably
|> xdvi -- will barf).

Quite likely. On an incomplete TeX file you will simply not get
a dvi file. Another synchronization problem:
The postamble of a dvi file contains a lot of information
and although I've seen some previewers (I remember one on the Atari ST)
that could handle incomplete dvi files, most of them give up.

|> Milt Epstein

Victor.