Am Donnerstag, dem 22.04.2021 um 13:18 -0400 schrieb Scott Kostyshak: > I wonder if using branches would be a better way to achieve the > desired workflow above. I believe we should preserve the previous > default behavior of giving an error in the GUI when there is a > missing included file.
But only since warnings are not salient enough on the command line, right? If so this fix is at the wrong place. > A couple of notes on issues related to the above. I think that they > could be worked around if we decide that a warning is better than an > error: > > 1. I think that LyX should try its best to export the same LaTeX code > on > different systems. I understand that in some cases it is difficult > to > avoid different exported code on different systems (I think we > sometimes condition on which features are available?), but it > would > be nice to keep those cases to a minimum. After this commit, if > the > file exists on one system but does not exist on a different > system, > LyX exports different LaTeX code. Perhaps as an alternative LyX > could > add code to the preamble to redefine the \include command for > LaTeX > to check if the file exists and condition accordingly. I really > don't > like this idea but at least the same .tex code would be exported > in > all cases. Thus the warning to indicate that something is unusual. I think an error is much too brute here, as it disallows people to work with this file. > 2. Starting with this commit, if you view the source code (e.g., set > to > "Complete Source"), every time you type a character you get the > warning. This also can be addressed at the core I think. > > > Can we have warnings on the cl that require user prompts before the > > process continues? > > Perhaps we could try to emulate what LaTeX does. They have prompts > for > undefined commands and if you press return the compilation tries to > continue. They also have a batch mode where there is no prompt and it > just errors out. I don't really like this idea of adding this > prompt-like behavior to LyX's command-line export and an additional > batch mode (preference?), but perhaps we could consider it if that's > what the majority prefers. In any case, we might want to figure this > out > after we figure out the GUI behavior discussed above. Note that I mean this as an option for warning which we think require attention (but are not errors). We could add an option "cl_confirmation" to alert::warning, defaulting to false and enabled for this particular warning. Jürgen > > Scott
signature.asc
Description: This is a digitally signed message part
-- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
