From: Jan Willem Flamma <jwfregister@icloud.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Couple of questions
Date: Mon, 31 Jul 2017 17:34:38 +0200 [thread overview]
Message-ID: <C1E22666-8A37-4C48-B344-8C8D818A8C1B@icloud.com> (raw)
In-Reply-To: <feadd156-2c34-52ad-901b-0a72976a9e54@gmx.es>
[-- Attachment #1.1: Type: text/plain, Size: 1518 bytes --]
Dear Pablo,
I experienced the same caption numbering issue late 2015.
See https://www.mail-archive.com/ntg-context@ntg.nl/msg80129.html <https://www.mail-archive.com/ntg-context@ntg.nl/msg80129.html> and https://www.mail-archive.com/ntg-context@ntg.nl/msg80131.html <https://www.mail-archive.com/ntg-context@ntg.nl/msg80131.html>
Can’t really recall exactly but probably found the answer eventually via the test suite (see http://www.pragma-ade.com/download-1.htm <http://www.pragma-ade.com/download-1.htm>)
Regards,
Jan Willem
> On 31 Jul 2017, at 17:15, Pablo Rodriguez <oinos@gmx.es> wrote:
>
> On 07/31/2017 08:01 AM, Jan Willem Flamma wrote:
>> Dear Gerion,
>>
>> Add
>>
>> \setuphead[subsubsection]
>> [incrementnumber=no]
>
> Dear Jan Willem,
>
> do you have an explanation for that behaviour?
>
> At least to me, it isn’t very intuitive (I’m trying to understand).
>
> Many thanks for your help,
>
> Pablo
> --
> http://www.ousia.tk
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________
[-- Attachment #1.2: Type: text/html, Size: 2691 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
___________________________________________________________________________________
next prev parent reply other threads:[~2017-07-31 15:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-28 0:22 Gerion Entrup
2017-07-28 0:35 ` Aditya Mahajan
2017-07-28 5:50 ` Jan Willem Flamma
2017-07-28 14:34 ` Pablo Rodriguez
2017-07-28 17:19 ` Gerion Entrup
2017-07-28 15:05 ` Pablo Rodriguez
2017-07-29 2:45 ` Gerion Entrup
2017-07-29 9:13 ` Pablo Rodriguez
2017-07-30 20:51 ` Gerion Entrup
2017-07-31 6:01 ` Jan Willem Flamma
2017-07-31 13:32 ` Gerion Entrup
2017-07-31 15:15 ` Pablo Rodriguez
2017-07-31 15:34 ` Jan Willem Flamma [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-07-03 15:58 abbg770
2008-07-03 16:07 ` 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=C1E22666-8A37-4C48-B344-8C8D818A8C1B@icloud.com \
--to=jwfregister@icloud.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).