ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: setupinteraction and macroexpansion
Date: Tue, 19 Jun 2012 11:08:13 +0200	[thread overview]
Message-ID: <2C224AA9-C0A7-4387-BBB7-F48646BE7206@googlemail.com> (raw)
In-Reply-To: <11410450325.20120619105929@gmx.de>


Am 19.06.2012 um 10:59 schrieb Andreas Schneider:

> On Tuesday, June 19, 2012, at 10:42 Wolfgang Schuster wrote:
> 
>> Am 19.06.2012 um 10:39 schrieb Andreas Schneider:
> 
>>> Hello,
>>> 
>>> I'm  a bit lost with macro expansion here. I try to use some macros to
>>> set  the title (and subject) of the PDF document. The attached minimal
>>> example shows what I want to achieve.
>>> 
>>> I tried def, edef, gdef, define, explicit expand, expandoneafter, etc.
>>> etc.  without  any  success. Whatever I do, the title field in the PDF
>>> metadata  always  contains  the  raw "\date..." command instead of the
>>> formatted date.
>>> 
>>> Any suggestions?
> 
>> You can’t use \date (or any other unexpandable command) in an expandable context.
> 
>> Wolfgang
> 
> Hmm  I  see, so \date is simply not possible for that case. Ok, thanks
> for  explaining  that  I wasn't aware (until now) that commands can be
> unexpandable.

To explain it in a simple way: Commands which can be used in \edef\comecommand{…}
are expandable and commands which fail in \edef are unexpandable. It’s also important
to know that commands with optional arguments are always unexpandable because
the underlying mechanism to check for the optional bracket, brace etc. can’t be used
in \edef, you can also make a expandable command (e.g. \def\foo{FOO}) unexpandable
by adding \unexpanded in front of the \def (e.g. \unexpanded\def\bar{BAR}).

Wolfgang
___________________________________________________________________________________
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:[~2012-06-19  9:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-19  8:39 Andreas Schneider
2012-06-19  8:42 ` Wolfgang Schuster
2012-06-19  8:59   ` Andreas Schneider
2012-06-19  9:08     ` Wolfgang Schuster [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=2C224AA9-C0A7-4387-BBB7-F48646BE7206@googlemail.com \
    --to=schuster.wolfgang@googlemail.com \
    --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).