From: Simon Pepping <spepping@scaprea.hobby.nl>
Subject: Re: Expansion problem in natural table
Date: Tue, 18 Feb 2003 21:11:52 +0100 [thread overview]
Message-ID: <20030218201152.GA1225@scaprea> (raw)
In-Reply-To: <5.1.0.14.1.20030209212337.0321af18@remote-1>
On Sun, Feb 09, 2003 at 09:26:27PM +0100, Hans Hagen wrote:
> At 09:52 PM 2/8/2003 +0100, Simon Pepping wrote:
>
> ah, the umlauts ...
>
> even if it would work out ok, it looks to ugly, so how about:
>
> \def\somethingsimon{blabla}
>
> \bTABLE
> \bTR\safeexpanded{\bTD\Aumlaut}\eTD\eTR
> \bTR\safeexpanded{\bTD\noexpand\somethingsimon\Aumlaut}\eTD\eTR
> \eTABLE
>
> with in enco-ini:
>
> \appendtoks
> \keepencodedtokens
> \to \everysafeexpanded
>
> and in syst-gen:
>
> \newtoks\everysafeexpanded
>
> \long\def\safeexpanded#1%
> {\begingroup
> \the\everysafeexpanded\long\xdef\@@expanded{\noexpand#1}%
> \endgroup
> \@@expanded}
>
> A more contexy alternative -)
This works fine, provided \keepencodedtokens exists, which is only in
more recent context versions.
Regards, Simon
--
Simon Pepping
email: spepping@scaprea.hobby.nl
prev parent reply other threads:[~2003-02-18 20:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-08 20:52 Simon Pepping
2003-02-09 18:39 ` Simon Pepping
2003-02-09 20:43 ` Hans Hagen
2003-02-09 20:26 ` Hans Hagen
2003-02-18 20:11 ` Simon Pepping [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=20030218201152.GA1225@scaprea \
--to=spepping@scaprea.hobby.nl \
--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).