From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Philipp Gesang <gesang@stud.uni-heidelberg.de>
Subject: Re: [supp-fil.mkiv] \openoutputfile & braces
Date: Sun, 29 May 2011 13:52:16 +0200 [thread overview]
Message-ID: <4DE23370.7010104@wxs.nl> (raw)
In-Reply-To: <20110528080759.GA24836@aides>
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
-----------------------------------------------------------------
___________________________________________________________________________________
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
___________________________________________________________________________________
prev parent reply other threads:[~2011-05-29 11:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-28 8:08 Philipp Gesang
2011-05-29 11:52 ` Hans Hagen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4DE23370.7010104@wxs.nl \
--to=pragma@wxs.nl \
--cc=gesang@stud.uni-heidelberg.de \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).