From: luigi scarso <luigi.scarso@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: \dorecurse and \recurselevel in Natural Tables
Date: Thu, 5 Mar 2009 15:23:57 +0100 [thread overview]
Message-ID: <fe8d59da0903050623i156b7a73g1192e1a00d3016fb@mail.gmail.com> (raw)
In-Reply-To: <5C45A695-1A90-412C-9C91-02A09F782F5C@gmail.com>
On Thu, Mar 5, 2009 at 2:52 PM, Wolfgang Schuster
<schuster.wolfgang@googlemail.com> wrote:
>
> Am 05.03.2009 um 14:23 schrieb luigi scarso:
>
>>> http://texblog.net/latex-archive/plaintex/expandafter/
>>
>> hey, this is not a "moderate use of expandafter" as I intended ..
>> I dropped latex for similar examples .
>> In this situation
>> "please, grep setvalue base/*"
>
> ??? I can't understand the relation between \setvalue and the expandafter
> trick in the example on the webpage, setvalue hides the csname ... endcsname
> part but the example tries to avoid the \let\oldmacro\macro
> \def\macro{\oldmacro...}
> redefinition.
I don't like the
\let\oldmacro\macro \def\macro{\oldmacro...}
construct
because sometimes the \def\macro{\oldmacro...}
can cause unexpected behaviour
I prefear
\setvalue{quote small}{\quote\small}
{\getvalue{quote small} foo }
--
luigi
___________________________________________________________________________________
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 : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2009-03-05 14:23 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-04 19:35 Curious Learn
2009-03-04 19:53 ` luigi scarso
2009-03-04 20:04 ` luigi scarso
2009-03-05 0:17 ` luigi scarso
2009-03-05 11:09 ` Wolfgang Schuster
2009-03-05 11:27 ` luigi scarso
2009-03-05 12:00 ` Wolfgang Schuster
2009-03-05 13:23 ` luigi scarso
2009-03-05 13:52 ` Wolfgang Schuster
2009-03-05 14:23 ` luigi scarso [this message]
2009-03-05 14:53 ` Wolfgang Schuster
2009-03-05 15:08 ` luigi scarso
2009-03-06 3:05 ` Aditya Mahajan
2009-03-06 6:41 ` luigi scarso
2009-03-06 10:47 ` Wolfgang Schuster
2009-03-06 11:20 ` Willi Egger
2009-03-06 13:01 ` Curious Learn
2009-03-06 13:32 ` Arthur Reutenauer
2009-03-06 16:15 ` Curious Learn
2009-03-06 13:35 ` luigi scarso
2009-03-06 14:49 ` Wolfgang Schuster
2009-03-06 16:33 ` Aditya Mahajan
2009-03-06 17:07 ` Wolfgang Schuster
2009-03-06 16:38 ` Aditya Mahajan
2009-03-04 20:35 ` Wolfgang Schuster
2009-03-04 20:57 ` Curious Learn
2009-03-04 21:11 ` Wolfgang Schuster
2009-03-04 21:43 ` Aditya Mahajan
2009-03-04 21:51 ` Wolfgang Schuster
2009-03-04 22:17 ` Curious Learn
2009-03-04 22:35 ` Wolfgang Schuster
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=fe8d59da0903050623i156b7a73g1192e1a00d3016fb@mail.gmail.com \
--to=luigi.scarso@gmail.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).