Hi Alfe,Isn't it a little bit overkill :-). Really, if you
It would be much better if the production of the pdf or of the new document
were treated as background jobs, so that the user could continue to interact
with the program during their completion.
To solve this problem, TeXmacs would have to create the PDF from an internally created copy of the current document (whose creation might be a similar long-running task as the PDF creation).
I think it should work exactly as you say. Just copying the document is not a
long-running task because it involves no computation at all. More precisely,
what you would do would be to pipe the document to a separate job that would
do
the processing.
I think the convenience of not having to stop working until the end of the
process is huge.
It breaks the continuity of your work. For instance, I may beAnother (much more simple) solution: open
willing to see the results of work done on one section and meanwhile start
looking at the following section, but I cannot do it because the pdf takes
some
minute to be composed (and it's not in the background as it could be).
Archive powered by MHonArc 2.6.19.