ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
Cc: Tobias Burnus <tobias.burnus@physik.fu-berlin.de>, ntg-context@ntg.nl
Subject: Re: \stretched{foo \bar} problems with expansion of \bar
Date: Mon, 10 Dec 2001 09:53:47 +0100	[thread overview]
Message-ID: <5.1.0.14.1.20011210095053.038ce290@server-1> (raw)
In-Reply-To: <3C0FF1BD.D9B20408@quicknet.nl>

At 11:31 PM 12/6/2001 +0100, Taco Hoekwater wrote:
>Tobias Burnus wrote:
> >
> > Hi,
> >
> > First I'd like to thank Taco for the calculation work, it works
> > like a charm :-)
>
>You're welcome :)
>
> > I have:
> >   \def\Semester{Wintersemester 2001/2002}
> >   \stretcheduppercase{VORLESUNGSKRITIK ZUM \Semester}
> >   \bye
>
>\expanded{\stretcheduppercase{VORLESUNGSKRITIK ZUM \Semester}}

this is indeed the way to go; for those unfamiliar with the \expanded macro 
(not a primitive): the first thing encountered is *not* expanded, which is 
what one often wants, like in

   \expanded{\somekindofcommand{the stuff to be expanded}

it even works well in cases like:

   \expanded{\somecommand[first not yet expanded arg]}[second already 
expanded arg]

which is more unreadable but faster than

   \expanded{\somecommand[....][...]}

i something should not be expanded inside \expanded, precede it by 
\noexpand (except for the first token)

Hans
-------------------------------------------------------------------------
                                   Hans Hagen | PRAGMA ADE | pragma@wxs.nl
                       Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
  tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------


      reply	other threads:[~2001-12-10  8:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-06 14:11 Tobias Burnus
2001-12-06 16:16 ` Christopher Creutzig
2001-12-06 22:31 ` Taco Hoekwater
2001-12-10  8:53   ` 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=5.1.0.14.1.20011210095053.038ce290@server-1 \
    --to=pragma@wxs.nl \
    --cc=ntg-context@ntg.nl \
    --cc=tobias.burnus@physik.fu-berlin.de \
    /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).