[supp-fil.mkiv] \openoutputfile & braces
![](https://secure.gravatar.com/avatar/5ef3be2c0e949ae4c891de058ebf4d76.jpg?s=120&d=mm&r=g)
Hi all, the mkiv definition of \openoutputfile adds undesired braces to filenames like “{out}.testfile2” and “{out.testfile3}”. ··8<····························································· \newwrite \testme %\openout \testme \jobname.testfile %%% works \openoutputfile \testme \jobname.testfile2 \openoutputfile \testme {\jobname.testfile3} \starttext irrelevant \stoptext ··8<····························································· mkii is fine. (Although I prefer plain \openout.) Philipp
![](https://secure.gravatar.com/avatar/49e63acb01f2ca80efce7eed08310ce8.jpg?s=120&d=mm&r=g)
On 28-5-2011 10:08, Philipp Gesang wrote:
Hi all,
the mkiv definition of \openoutputfile adds undesired braces to filenames like “{out}.testfile2” and “{out.testfile3}”.
··8<·····························································
\newwrite \testme %\openout \testme \jobname.testfile %%% works \openoutputfile \testme \jobname.testfile2
here #1 = \jobname so you get what you ask for
\openoutputfile \testme {\jobname.testfile3}
\starttext
irrelevant
\stoptext
··8<·····························································
mkii is fine. (Although I prefer plain \openout.)
it's a macro and not a syntactically equivalent to \open* so indeed you need to use braces even if you use \openin you need to be careful as then the space or \relax is a delimited, so you can get side effects when used as: \def\MyOpenIn{\openin\MyIn\jobname} \MyOpenIn bla Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
participants (2)
-
Hans Hagen
-
Philipp Gesang