ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: 19cat <di@nou.cat>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Parameter "first" of \setupindenting works?
Date: Tue, 2 Dec 2014 15:12:52 +0000	[thread overview]
Message-ID: <14596878-F3C2-41CE-9A34-2D9B3AB807B9@nou.cat> (raw)
In-Reply-To: <40AEF23D-25C2-4D94-B9B6-C06EB0E0B455@gmail.com>

Well, I understood that:
 - indent first paragraph after heads is configured with "indentnext" of \setuphead .
 - "first/next" option of \setupindenting refers only first paragraf of document before heads.

That is correct?

19cat

El 02/12/2014, a les 9:49 a.m., Wolfgang Schuster <schuster.wolfgang@gmail.com> va escriure:
> 
>> Am 02.12.2014 um 08:33 schrieb 19cat <di@nou.cat>:
>> 
>> I have another question, using this \setupheads solution.
>> 
>> When I use \title and \subject the result of "first" and "next" options of \setupindenting are omitted.
>> 
>> While in \chapter and \sections with \setupheads[indentnext={yes,first}] command, first paragraph indent is controled with "first/next" option in \setupindenting[yes,medium,next], in \title and \subject only change modifying indentnext to yes/no in  \setuphead[subject].
>> 
>> Is this normal?
> 
> The indentnext key accepts only the three values
> 
>  - yes,
>  - no and
>  - auto.
> 
> Other values like your “yes,first” (which is here a single keyword with a comma in the name and not a list) are ignored by context.
> 
> 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
> ___________________________________________________________________________________
___________________________________________________________________________________
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
___________________________________________________________________________________

  reply	other threads:[~2014-12-02 15:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-01 14:55 19cat
2014-12-01 18:00 ` Pablo Rodriguez
2014-12-01 18:45   ` 19cat
2014-12-01 18:54     ` Aditya Mahajan
2014-12-01 19:05       ` 19cat
2014-12-01 20:23         ` Pablo Rodriguez
2014-12-02  4:16           ` 19cat
2014-12-02  7:33           ` 19cat
2014-12-02  9:49             ` Wolfgang Schuster
2014-12-02 15:12               ` 19cat [this message]
2014-12-06 11:29                 ` Pablo Rodriguez
2014-12-06 11:39                   ` 19cat
2014-12-06 17:29                   ` Aditya Mahajan
2014-12-02 17:26               ` 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=14596878-F3C2-41CE-9A34-2D9B3AB807B9@nou.cat \
    --to=di@nou.cat \
    --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).