Hi.

Suppose I have a file "test.tex":

%%%%% cut here %%%%%
\starttext

Hello

\stoptext
%%%%% cut here %%%%%

Suppose someone (I'm not mentioning any names) has a typo in a shell script
and accidentally runs the command
        context 'test.tex}'

On the good side, the first line of terminal output is

        mtx-context     | warning: no (local) file './test.tex}', proceeding

But who looks at the first line?  Especially since it only says "warning"
and not "error".

Later terminal output says
        ...
        close source    > level 1, order 1, name 
'/usr/local/context/tex/texmf-context/tex/context/base/mkxl/cont-new.mkxl'
        tex error       > tex error on line 7 in file : Argument of 
\setupsystem has an extra }
        
        m={1},inputfile={./test.tex}
        
        <inserted text> 
            
            \par }
        <lua input> 
        <everyjob> 
            ...llfont 786432\scaledpoint \fontextraspace \nullfont 
85459\scaledpoint \publ_specification_set {\btxparameter \c!specification 
}\showcontextbanner \calculatecurrenttime \syst_files_load \setupoutput 
[pdf]\clf_setdocumentcommandline 
            \clf_setdocum ...
        <token input> 
            }
        <initial input> 
            
        
        <empty file>
        I've run across a '}' that doesn't seem to match anything. For example,
        '\def\a#1{...}' and '\a}' would produce this error. The '\par' that 
I've just
        inserted will cause me to report a runaway argument that might be the 
root of the
        problem.
        mtx-context     | fatal error: return code: 1

by which time the first line has scrolled so far away it is said to be
vacationing in Portugal.

Focusing on things starting with
        tex error       > tex error on line 7 in file : Argument of 
\setupsystem has an extra }
it is not clear (at least to some people who foolishly append '}' to their
file names) what the error is.

So...

Does it make sense for context to proceed when the requested file can't be
found?

(Assuming that answer is "yes", why?)


Bonus question: given that the input file can't be found because there is a
spurious '}' at the end, why does ConTeXt (apparently) process that '}',
which it apparently thought was part of the file name it couldn't find ?

Thanks.

                                        Jim
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : [email protected] / 
https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage  : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive  : https://github.com/contextgarden/context
wiki     : https://wiki.contextgarden.net
___________________________________________________________________________________

Reply via email to