From: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
To: Aditya Mahajan <adityam@umich.edu>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Bug with linenumbering
Date: Thu, 3 May 2012 18:01:49 +0200 [thread overview]
Message-ID: <C68ADACA-1A7D-4EB0-B8B4-87A6B6583830@googlemail.com> (raw)
In-Reply-To: <alpine.LNX.2.02.1205031109160.1834@ybpnyubfg.ybpnyqbznva>
Am 03.05.2012 um 17:18 schrieb Aditya Mahajan:
> On Thu, 3 May 2012, Wolfgang Schuster wrote:
>
>> You assume \definelinenumbering has a second argument for the settings but this isn’t the case
>
> D'oh.
>
>> and you need \setuplinenumbering to set them.
>
> I also needed to change \setvalue to \setevalue in the example, and add an \expanded to get it to work.
In MkIV \setuevalue is better the \setevalue and \normalunexpanded is faster than \expanded.
The problem in your approach is that you can only set the style and color value with \definewhatever
where I think it’s better to use \setupwhatever.
\unprotect
\installnamespace {whatever}
\installcommandhandler \????whatever {whatever} \????whatever
\appendtoks
\definelinenumbering[\currentwhatever]%
\to \everydefinewhatever
\appendtoks
\setuevalue{\e!start\currentwhatever}{\whatever_start[\currentwhatever]}%
\setuevalue{\e!stop\currentwhatever }{\whatever_stop }%
\to \everydefinewhatever
\appendtoks
\normalexpanded{\setuplinenumbering
[\currentwhatever]
[\c!color=\whateverparameter\c!numbercolor,
\c!style=\whateverparameter\c!numberstyle]}%
\to \everysetupwhatever
\unexpanded\def\whatever_start[#1]%
{\begingroup
\edef\currentwhatever{#1}%
\startlinenumbering[\currentwhatever]}
\unexpanded\def\whatever_stop
{\stoplinenumbering
\endgroup}
\protect
\definewhatever[testing][numbercolor=red,numberstyle=bold]
\setupwhatever [testing][numbercolor=blue]
\starttext
\starttesting
\input knuth
\stoptesting
\stoptext
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
___________________________________________________________________________________
next prev parent reply other threads:[~2012-05-03 16:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-01 19:43 Aditya Mahajan
2012-05-01 22:16 ` Aditya Mahajan
2012-05-02 8:30 ` Hans Hagen
2012-05-03 4:58 ` Aditya Mahajan
2012-05-03 12:43 ` Wolfgang Schuster
2012-05-03 15:18 ` Aditya Mahajan
2012-05-03 16:01 ` Wolfgang Schuster [this message]
2012-05-03 18:59 ` Aditya Mahajan
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=C68ADACA-1A7D-4EB0-B8B4-87A6B6583830@googlemail.com \
--to=schuster.wolfgang@googlemail.com \
--cc=adityam@umich.edu \
--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).