From: Lars Huttar <lars_huttar@sil.org>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: confusion about expansion
Date: Wed, 12 Mar 2014 10:51:14 -0400 [thread overview]
Message-ID: <53207462.4020909@sil.org> (raw)
In-Reply-To: <314F455E-CFD1-4496-9523-83CCDCC47EC2@gmail.com>
On 3/12/2014 10:21 AM, Wolfgang Schuster wrote:
>
> Am 12.03.2014 um 15:12 schrieb Lars Huttar <lars_huttar@sil.org
> <mailto:lars_huttar@sil.org>>:
>
>> On 3/12/2014 10:05 AM, Wolfgang Schuster wrote:
>>> Am 12.03.2014 um 15:00 schrieb Lars Huttar <lars_huttar@sil.org
>>> <mailto:lars_huttar@sil.org>>:
>>>
>>>> Hello,
>>>> I've got a running page head like this in my document:
>>>>
>>>> \def\CurrentUser{\cldcontext{os.resultof"whoami"}}
>>>>
>>>> \def\Markname { Compiled \date by \CurrentUser \LUATEX +\ConTeXt\
>>>> \contextversion }
>>>>
>>>> and later:
>>>>
>>>> \setlayer[cropmark][preset=lefttop,x=3cm,y=-1.5\lineheight]{\Markname}
>>>>
>>>> But when I run this, I get a UCS error that seems to indicate that the
>>>> *result* of \CurrentUser ("waxhaw\huttar") is getting parsed as a
>>>> command sequence.
>>> When you want to pass a backslash to Lua you have to use
>>> \letterbackslash.
>>>
>>
>> Thanks... can you give me an example of what that would look like?
>> I don't think I want to pass a backslash to Lua, so I'm not sure how to
>> apply what you're saying. Or are you using "Lua" here in the sense of
>> LuaTeX?
>>
>> A backslash appears in the output of os.resultof"whoami"; do I need to
>> perform some processing on that output in order to escape backslashes?
>
> Try this:
>
> \def\CurrentUser{\cldcontext{os.resultof"whoami"}}
>
> \def\Markname{Compiled \date by \detokenize\expandafter{\CurrentUser}
> \LUATEX +\ConTeXt\ \contextversion.}
>
> \setuplayout[location=middle,marking=on]
>
> \definelayer[cropmark][state=repeat,width=\paperwidth,height=\paperheight]
>
> \setupbackgrounds[page][background=cropmark]
>
> \setlayer[cropmark][preset=lefttop,x=3cm,y=1.5\lineheight]{\Markname}
>
> \starttext
>
> Foo
>
> \stoptext
>
>
Thanks again...
This gets rid of the error, but it seems to prevent any expansion of the
content of \CurrentUser, because the page head now literally looks like
this:
Compiled March 12, 2014 by \cldcontext {os.resultof"whoami"}.
LuaTEX+ConTEXt...
Lars
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2014-03-12 14:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-12 14:00 Lars Huttar
2014-03-12 14:05 ` Wolfgang Schuster
2014-03-12 14:12 ` Lars Huttar
2014-03-12 14:21 ` Wolfgang Schuster
2014-03-12 14:51 ` Lars Huttar [this message]
2014-03-12 15:06 ` Wolfgang Schuster
2014-03-12 15:45 ` Lars Huttar
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=53207462.4020909@sil.org \
--to=lars_huttar@sil.org \
--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).