Le 05/04/11 10:24, Jean-Marc Lasgouttes a écrit :
Le 05/04/11 08:57, Guenter Milde a écrit :
Especially when hunting for an error, looking at what is generated so far
can be a great help. So, a button like: "open the output anyway" on the
error message box (if there is an output file) would be a great
improvement.
We should be careful to avoid the ``normal'' latex workflow I have seen
too often: ``just type return whenever LaTeX stops until compilation is
finished; this is normal''. I understand the use case described above,
but having people produce documents with errors they do not understand
is not helping them in the end.
JMarc
The current LyX workflow seems to me as already a "normal" Latex
workflow: latex is run in no-stop-mode and the total set of errors are
presented in the end. The "open the output anyway" would fit in this
context as both:
- a poweruser feature : "i know already where this error comes from, but
i decide it is not a priority because i want my draft now, even if it is
incomplete";
- a beginner feature : "i have no idea what this error message means,
but i can see on the output document that it is not what i want and that
there are issues from this place; let's investigate the problem".
- a lazy user feature : "i don't mind if my document is crippled, i will
not even try to figure out why". Of course these users will not really
use Lyx/Latex to its full potential, but they didn't have high needs
anyway, did they ? ;-)
More seriously, Latex errors can be sometimes cryptic; Lyx is already
protecting us from them for many basic uses (arrays, unmatched
begin/end, {, $...), but when using it to build more complex documents,
I don't see how one could avoid having to investigate those errors.
Rémi
