On 17/04/2017 21:24, Kornel Benko wrote:
Btw, instead of ending each test with \Ax, what about ending them with \Cq ?
(shortcut for File->Quit) ?
Or \Axlyx-quit\[Return], this is language independent. OTOH, maybe we have to
wait before sending it.
I tried, and lyx often missed some keystrokes ...
The problem here is that the buffer may be dirty. E.g. you get a dialog for
save, discard, or abort.
and, some tests might just end in the Wraparound? question, succeeding if nothing is
found, without any attempt to reply "No" to the wraparound Q.
In all these cases, after the first attempt of grafceful shutdown, keytest.py
would fall back to kill -9, which fixes also the case of
And what if lyx is in an endless loop? (Should not be, but who knows)
this.
Nice, but we should wait some seconds before using kill -9 the first time
that's one of the drawbacks of a clean shutdown, we'd have to wait for it,
slowing down tests. Perhaps alternate ways might be to just kill -9 as it is
already now, but introduce:
-) either a command-line option to force lyxerr << flush on every LYXERR()
call, that we'd only use on tests
-) or a special minibuffer command to flush lyxerr
-) or flush lyxerr on signal, and shutdown with that signal.
Thoughts?
T.
