From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: position of linenumbering
Date: Wed, 12 Oct 2016 18:22:49 +0200 [thread overview]
Message-ID: <86a8cc7f-2ce7-9ed8-7a4b-2ca291ff6f85@wxs.nl> (raw)
In-Reply-To: <58de29c0-b870-de6b-1081-d08a8df47d34@uni-bonn.de>
On 10/12/2016 5:58 PM, Thomas A. Schmitz wrote:
> On 12.10.2016 16:38, Pablo Rodriguez wrote:
>> Wolfgang,
>>
>> your approach is right, but hasn’t Thomas hit a bug?
>>
>> According to the description from page 301 in i-context.pdf,
>> \startlinenumbering ... \stoplinenumbering inherit from
>> \setuplinenumbering.
>
>
> Thanks Wolfgang, this solution works (I must admit I wasn't aware of
> \definelinenumbering). Nevertheless, I think Pablo is right because this
> means one must define every setup in advance. In some situations, it
> might be useful to change on the fly, and I think this "bleeding" of
> setups into preceding blocks is unexpected.
\startlinenumbering [location=text,distance=0.5cm]
\dorecurse{2}{\input tufte} \page
\stoplinenumbering
line number placement is delayed till a page is constructed (only then
do we know where the margins are) and settings get reset after
\stoplinennumbering
(there are more cases when grouping can interfere with pagebreaks after
the group ends)
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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://context.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2016-10-12 16:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-12 13:38 Thomas A. Schmitz
2016-10-12 13:48 ` Otared Kavian
2016-10-12 14:18 ` Thomas A. Schmitz
2016-10-12 14:25 ` Wolfgang Schuster
2016-10-12 14:38 ` Pablo Rodriguez
2016-10-12 15:58 ` Thomas A. Schmitz
2016-10-12 16:22 ` Hans Hagen [this message]
2016-10-12 16:03 ` Wolfgang Schuster
2016-10-12 16:49 ` Pablo Rodriguez
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=86a8cc7f-2ce7-9ed8-7a4b-2ca291ff6f85@wxs.nl \
--to=pragma@wxs.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).