Re: [NTG-context] texexec/context error messages [MkIV]
Aditya Mahajan (2010-05-23 13:24): On Sun, 23 May 2010, Rogutės Sparnuotos wrote: And, the initial reason for these questions: has anyone figured out an appropriate 'errorformat' for the 'vim' editor, for use with MkIV? The one at http://www.vim.org/scripts/script.php?script_id=1925 seems to be working with MkII only... Hans, does LuaTeX support -file-line-error flag like pdftex? If so, how do I pass that (context --passon=-file-line-error) does not seem to work. Rogutes, if you want to match system : module * not found Add \%+Asystem\ %#:\ module\ %m\ not\ found, to the error format (it will not jump to the line containing \usemodule[...] because that information is not available in the log file). Thanks, Aditya. I hope a 'file-line-error'-like option will turn up eventually :) One more question regarding error reporting: why are invalid parameters to commands _silently_ ignored? 'texexec --verbose' outputs the same, be it run with \setupheads[align=abc123,heads=lotsoff] or with \setupheads[align=center] Since there is no documentation describing the numerous parameters of most of the commands, I think it would be really useful to support the trial and error method by showing as much parsing errors as possible... -- -- Rogutės Sparnuotos ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
[NTG-context] texexec/context error messages [MkIV] [vim]
G'day, Shouldn't ConTeXt be stopping on system : module simplefonts not found instead of stopping on problems appearing only later, e.g. ! Undefined control sequence. recently read \setmainfont Shouldn't error messages like the first one be more noticeable? Why doesn't ConTeXt set an exit code when running in --batchmode or --nonstopmode? And, the initial reason for these questions: has anyone figured out an appropriate 'errorformat' for the 'vim' editor, for use with MkIV? The one at http://www.vim.org/scripts/script.php?script_id=1925 seems to be working with MkII only... -- -- Rogutės Sparnuotos ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] texexec/context error messages [MkIV] [vim]
On Sun, 23 May 2010, Rogutės Sparnuotos wrote: And, the initial reason for these questions: has anyone figured out an appropriate 'errorformat' for the 'vim' editor, for use with MkIV? The one at http://www.vim.org/scripts/script.php?script_id=1925 seems to be working with MkII only... Hans, does LuaTeX support -file-line-error flag like pdftex? If so, how do I pass that (context --passon=-file-line-error) does not seem to work. Rogutes, if you want to match system : module * not found Add \%+Asystem\ %#:\ module\ %m\ not\ found, to the error format (it will not jump to the line containing \usemodule[...] because that information is not available in the log file). Aditya ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___