ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "F. Miller Maley" <maley@idaccr.org>
Subject: Re: Distinguished item in \placelist?
Date: Fri, 07 Dec 2001 01:20:42 -0500	[thread overview]
Message-ID: <3C105FB0.9BD5779D@idaccr.org> (raw)
In-Reply-To: <5.1.0.14.1.20011203105421.02f070a8@server-1>

Hans Hagen wrote:
> Say that I patch a macro :
> 
> \unprotected \def\dolijstelement#1#2#3#4#5#6% pas op: wordt ook elders
> gedefinieerd
>    {\doiftoclevelelse[#5]
>       {\def\currentlist{#1}%
>        \ifundefined{\??li\currentlist\c!huidige}\else
>          \doif{#3}\currentheadnumber
>            {\edef\currentlist{\getvalue{\??li\currentlist\c!huidige}}}%
>        \fi
>        \dodolijstelement\currentlist{#2}{#3}{#4}{#5}{#6}}
>       {}}
> 
> (this assumes a version where \currentheadnumber is known)
> etc.

After considerable hacking, I got this to work!  It didn't work as written
for various reasons, mainly having to do (as far as I could tell) with the
order in which things are expanded, and the \ifundefined ... \else ... \fi
confusing TeX about \if...\fi nesting.  Anyway, the most serious problem
was that \currentheadnumber expands to a single number, but argument #3
is usually something like 1.2 or 1.2.3, the details depending on the level
and the "stopper".  I can hack around this problem in specific cases but
I don't have a general solution yet.  One plan would be to expand
\headnumber[#1] and compare it with #3, but \headnumber (or rather
\kopnummer) seems to be protected from expansion in eTeX.

I may be the only one voting for it, but I do think this would be a nifty
feature of ConTeXt.

-- Miller Maley


  reply	other threads:[~2001-12-07  6:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-01 20:19 F. Miller Maley
2001-12-03  9:58 ` Hans Hagen
2001-12-07  6:20   ` F. Miller Maley [this message]
2001-12-10 10:14     ` Hans Hagen

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=3C105FB0.9BD5779D@idaccr.org \
    --to=maley@idaccr.org \
    /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).