You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed that compile-commands-until-done sets TeX-process-asynchronous to nil. When I hack it to set it to true, I sometimes get some concurrent LaTeX process running at the same time. Could it be avoided ? It's a pity having to wait for a long compile time when one could be writing the next part.
The text was updated successfully, but these errors were encountered:
Yes, that can be done by rewriting the function in terms of a process sentinel (or maybe hooks). It would take a bit of work though, and I probably won't have time for it.
Yes, that can be done by rewriting the function in terms of a process
sentinel (or maybe hooks). It would take a bit of work though, and I
probably won't have time for it.
Maybe I'll give it a try. Never used a sentinel before though.
Julien.
I noticed that compile-commands-until-done sets TeX-process-asynchronous to nil. When I hack it to set it to true, I sometimes get some concurrent LaTeX process running at the same time. Could it be avoided ? It's a pity having to wait for a long compile time when one could be writing the next part.
The text was updated successfully, but these errors were encountered: