ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Carlos via ntg-context <ntg-context@ntg.nl>
To: ntg-context@ntg.nl
Cc: Carlos <linguafalsa@gmail.com>
Subject: Re: [NTG-context] \setupitemize[indentnext=auto] broken?
Date: Sun, 16 Apr 2023 08:28:34 -0400	[thread overview]
Message-ID: <rcyji5ormpc5wkj2g6fweobjpl64wmfmfoo5cjhaak4czgeh57@gucb4w2swx67> (raw)
In-Reply-To: <ZDrenPNFYNBzOhd6@x360.localdomain>

On Sat, Apr 15, 2023 at 02:27:56PM -0300, Jim via ntg-context wrote:
> In the wiki page https://wiki.contextgarden.net/Indentation there is the
> following example:
> 
> %------------------------------------------------------------------------
> 
> \setupindenting[medium,yes]
> \setupitemize[indentnext=auto]
> 
>   \startitemize
>     \item One
>   \stopitemize
> 
>   This paragraph should be indented - due to the blank line after \type{\stopitemize}.
> 
>   \startitemize
>     \item Two
>   \stopitemize
>   This paragraph should not be indented.
> 
> %------------------------------------------------------------------------
> 
> Tragically, the paragraph which claims it should be indented is not, in
> both my test and the wiki page itself.
> 
> Is this a documentation bug, a ConTeXt bug, or something else yet?

I don't know. Why would it be a documentation bug if it clearly says it
should be indented only after the blank line,  unless \indent was omitted on
purpose while trying to make it look as if the blank line would  have
any effect after all. Makes no sense. 

\setupindenting[medium,yes]
\setupitemize[indentnext=auto]

\starttext
  \startitemize
    \item One
  \stopitemize\indent%blank line

This paragraph should be indented - due to the blank line after \type{\stopitemize}.

  \startitemize
    \item Two
  \stopitemize
  
\noindent{\dorecurse{10}{\indent This paragraph should not be indented.}}
\stoptext


> 
> Cheers.
> 
>                                 Jim
> ___________________________________________________________________________________
> If your question is of interest to others as well, please add an entry to the Wiki!
> 
> maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
> webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
> archive  : https://bitbucket.org/phg/context-mirror/commits/
> wiki     : https://contextgarden.net
> ___________________________________________________________________________________
> 

-- 
101 USES FOR A DEAD MICROPROCESSOR
	(1)  Scarecrow for centipedes
	(2)  Dead cat brush
	(3)  Hair barrettes
	(4)  Cleats
	(5)  Self-piercing earrings
	(6)  Fungus trellis
	(7)  False eyelashes
	(8)  Prosthetic dog claws
        .
        .
        .
	(99)  Window garden harrow (pulled behind Tonka tractors)
	(100) Killer velcro
	(101) Currency

___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : https://contextgarden.net
___________________________________________________________________________________

  parent reply	other threads:[~2023-04-16 12:29 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-15 17:27 Jim via ntg-context
2023-04-15 17:49 ` [NTG-context] https://wiki.contextgarden.net/Enumerations problem Jim via ntg-context
2023-04-16 12:28 ` Carlos via ntg-context [this message]
2023-04-16 16:24   ` [NTG-context] \setupitemize[indentnext=auto] broken? Jim via ntg-context
2023-04-19 12:23     ` Carlos via ntg-context
2023-04-16 16:35 ` Aditya Mahajan via ntg-context
2023-04-16 17:23   ` Jim via ntg-context
2023-04-17  5:06   ` Aditya Mahajan via ntg-context
2023-04-17 17:04     ` Hans Hagen via ntg-context
2023-04-18 13:48       ` Aditya Mahajan via ntg-context
2023-04-18 14:56         ` Hans Hagen via ntg-context

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=rcyji5ormpc5wkj2g6fweobjpl64wmfmfoo5cjhaak4czgeh57@gucb4w2swx67 \
    --to=ntg-context@ntg.nl \
    --cc=linguafalsa@gmail.com \
    /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).