From: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: problem with \getparameters
Date: Thu, 23 Feb 2012 14:00:42 +0100 [thread overview]
Message-ID: <5DAC1D23-0639-452A-A25D-34D1E45FBA62@googlemail.com> (raw)
In-Reply-To: <CAG5iGsB1d8FZT=H2hMv-_6ROfe00x1AEGLmM8g=MR23b1k+WwA@mail.gmail.com>
Am 23.02.2012 um 13:51 schrieb luigi scarso:
> On Thu, Feb 23, 2012 at 1:39 PM, Wolfgang Schuster
> <schuster.wolfgang@googlemail.com> wrote:
>>
>> Am 23.02.2012 um 13:31 schrieb luigi scarso:
>>
>>> Hm global effect.. you can use a namespaced one
>>>
>>> \enabletrackers[lines.numbers]
>>> \starttext
>>> Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod
>>> tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At
>>> vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd
>>> gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet.
>>> \vrule width\textwidth height 1pt\par
>>> \setuplinenumbering[Mine1][width=1cm,start=1]
>>
>> Better use first \define… and not \setup… which can result in an error for commands which
>> use the commandhandler (e.g. \definelayout[<name>][…] vs. \setuplayout[<name>][…]).
> yes, infact It was only to show the interference... I'm not sure if
> it's a bug or not.
>
> Anyway for this case \setup.. seems to inglobe \define...
>
> \unexpanded\def\definelinenumbering
> {\dosingleempty\dodefinelinenumbering}
>
> \def\dodefinelinenumbering[#1]%
> {\edef\currentlinenumbering{#1}%
> \mkdefinetextlinenumbering}
>
> \unexpanded\def\setuplinenumbering
> {\dodoubleempty\dosetuplinenumbering}
>
> \def\dosetuplinenumbering[#1][#2]%
> {\ifsecondargument
> \def\currentlinenumbering{#1}%
> \getparameters[\??rn#1][#2]%
> \else
> \let\currentlinenumbering\empty
> \getparameters[\??rn][#1]%
> \fi
> \mksetuptextlinenumbering}
\definelinenumbering doesn’t use the commandhandler (see mult-aux.mkiv) but this can change.
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-02-23 13:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-23 8:05 Thomas A. Schmitz
2012-02-23 11:27 ` Wolfgang Schuster
2012-02-23 11:42 ` Thomas A. Schmitz
2012-02-23 12:29 ` Wolfgang Schuster
2012-02-23 15:19 ` Thomas A. Schmitz
2012-02-23 12:31 ` luigi scarso
2012-02-23 12:39 ` Wolfgang Schuster
2012-02-23 12:51 ` luigi scarso
2012-02-23 13:00 ` Wolfgang Schuster [this message]
2012-02-23 13:08 ` luigi scarso
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=5DAC1D23-0639-452A-A25D-34D1E45FBA62@googlemail.com \
--to=schuster.wolfgang@googlemail.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).