From: Rik Kabel <context@rik.users.panix.com>
To: ntg-context@ntg.nl
Subject: Re: display current section number in \writestatus
Date: Thu, 9 Mar 2017 17:05:37 -0500 [thread overview]
Message-ID: <7c31e5f9-18f9-7eb9-2d63-6f4f34074134@rik.users.panix.com> (raw)
In-Reply-To: <f9aa8141-84a3-d772-24e3-6f5587e9af71@wxs.nl>
[-- Attachment #1.1: Type: text/plain, Size: 1448 bytes --]
On 2017-03-09 16:20, Hans Hagen wrote:
> On 3/9/2017 4:39 AM, Rik Kabel wrote:
>> ConTeXters,
>>
>> What is the best way to get the current section number in a basic format
>> (pt.ch.s.ss... as displayed in the log in structure sectioning entries)
>> for display in a custom log entry (via \writestatus)? I have tried
>> \fullheadnumber and such, but cannot find something appropriate.
>
> \writestatus{!!!!!!}{\getfullstructurenumber{\thenamedheadlevel{subsection}}}
>
>
Nope. With commands like these:
\starttexdefinition LogNote #NOTETEXT
\writestatus{Note}{{\getfullstructurenumber{\thenamedheadlevel{section}}:p.\pagenumber}
#NOTETEXT}
\stoptexdefinition
\LogNote{See http://www.thelatinlibrary.com/ter.eunuchus.html for
the original.}
and the note is in a section, I get:
Note > {\oldstylenumerals {1}\color
[red]{A·}\oldstylenumerals {8}:p.19} See
http://www.thelatinlibrary.com/ter.eunuchus.html for the original.
which reflects the formatting of the chapter and section numbers. But
worse, I have to track the section depth, because if the note is at a
different level there is nothing displayed for the sectioning. I want
the unformatted numbers as displayed in
structure > sectioning > section @ level 3 : 1.3.5 -> Group
authorship and works for hire
and if I do not have to track the level and recurse to pick up each
component that would be better.
--
Rik
[-- Attachment #1.2: Type: text/html, Size: 2469 bytes --]
[-- Attachment #2: Type: text/plain, Size: 492 bytes --]
___________________________________________________________________________________
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 : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2017-03-09 22:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-09 3:39 Rik Kabel
2017-03-09 21:20 ` Hans Hagen
2017-03-09 22:05 ` Rik Kabel [this message]
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=7c31e5f9-18f9-7eb9-2d63-6f4f34074134@rik.users.panix.com \
--to=context@rik.users.panix.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).