[AUCTeX] Minor ConTeXt questions

[Philipp Reichmuth]

Hi,

a couple of minor quirks and questions with respect to CVS and ConTeXt, 
mostly regarding context.el:

- Running texexec with '--passon="-interaction=nonstopmode"' apparently 
doesn't work at least with recent ConTeXt; if ConTeXt hits an error, the 
process hangs at TeX's ? prompt.  Instead, texexec has a --batchmode 
parameter that does the job; changing the values

- When running texexec with C-c C-C ConTeXt RET, the output isn't parsed 
correctly at present; you always.  The regexp in context.el ('^ 
TeX\\(Exec\\|Util\\)' doesn't match anything because of the initial 
space.  For me, using 'tuo file saved\nTeXExec | runtime:' instead does 
the job, but in a hackish sort of way, because unfortunately CoNTeXt 
currently doesn't produce much meaningful output in --batchmode (besides 
the return code).  If it hits any errors, this way you only get the 
information that something is wrong; if you want to know what exactly it 
is, you have to run it in interactive mode.  I guess one should

- I've been adding ConTeXt commands to the keyword classes in 
font-latex.el to get better syntax highlighting.  Doing this in a 
hardwired way is a bit unsatisfactory because CoNTeXt has a very large 
number of commands (basically what is \begin{XX}..\end{XX} in LaTeX 
becomes \startXX..\stopXX in ConTeXt), and because it supports commands 
in multiple languages.  I was thinking of adding a function to 
context.el that builds the font-latex-built-in-keyword-classes list 
dynamically depending on the current interface language.  Is there any 
substantial argument against this approach?

I keep adding little bits to my ConTeXt functions that eventually might 
be interesting for others as well.  What's the preferred way to submit 
them, shall I post patches here, send them to Berend for review, or 
something else?

Philipp

Philipp