ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Lars Huttar <lars_huttar@sil.org>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: confusion about expansion
Date: Wed, 12 Mar 2014 10:00:05 -0400	[thread overview]
Message-ID: <53206865.1090800@sil.org> (raw)

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.

Here's the error:

! Undefined control sequence.

 1 >>  % see ConTeXt wiki http://wiki.contextgarden.net/Imposition#Cut_marks
 2
 3     %% TODO: make sure this doesn't reevaluate every time
 4     %% the command sequence is used!
 5     \define\CurrentUser{\cldcontext{os.resultof"whoami"}}
 6
 7     \def\Markname { Compiled \date by \CurrentUser  \LUATEX
+\ConTeXt\ \conte
xtversion. SVN  }
...

l.1 waxhaw\huttar

\cldcontext #1x-\directlua {context(#1)}

\Markname #- Compiled \date by \CurrentUser
                                            \LUATEX +\ConTeXt \
\contextvers...
l.24 ...t=lefttop,x=3cm,y=-1.5\lineheight]{\Markname
                                                  }

How can I change the definition of \CurrentUser, or \Markname, to output
the result of \CurrentUser as-is, instead of parsing the result?
I tried (somewhat blindly) changing \def to \define, but it didn't make
any difference.

At the same time, I want to make sure that the processor won't be making
an OS system call to "whoami" every time \CurrentUser is evaluated: I
want it to happen only once, when \CurrentUser is defined.

Here is my complete working example:

\def\CurrentUser{\cldcontext{os.resultof"whoami"}}

\def\Markname { Compiled \date by \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 for any help.
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
___________________________________________________________________________________


             reply	other threads:[~2014-03-12 14:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-12 14:00 Lars Huttar [this message]
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
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=53206865.1090800@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).