ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Mikael P. Sundqvist" <mickep@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Prevent indentation after itemize
Date: Thu, 11 Apr 2019 12:48:25 +0200	[thread overview]
Message-ID: <CAHy-LL8HRcNJ+QEbkZaTtotfae-GxsgNYRPCit1=yWShHfPKkA@mail.gmail.com> (raw)
In-Reply-To: <op.zz2oljip62epfj@lpr>

On Thu, Apr 11, 2019 at 10:02 AM Procházka Lukáš Ing. <LPr@pontex.cz> wrote:
>
> Hello,
>
> Czech typo rules prefer not indenting paragraphs after itemization.
>
> How to setup indenting best to achieve this?
>
> The following code gives the desired output:
>
> ----
> \setupindenting[yes,big]
>
> \starttext
>    \section{Sec}
>
>    \input knuth
>
>    \startitemize[][after={\blank\noindent}]
>      \item Aaa
>      \item Bbb
>    \stopitemize
> % "%" JUST TO SUPPRESS BLANK LINE
>    \input knuth
> \stoptext
> ----
>
> but (obviously) forces user to suppress a blank line between \stopitemize and next text (thus "% JUST TO SUPPRESS BLANK LINE").
>
> Is there a way which would "gobble" next \par after \stopitemize to allow to write simply (without "% ... "):
>
> ----
> ...
>    \stopitemize
>                                           <- EMPTY LINE TO BE ALLOWED HERE
>    \input knuth
> ...
> ----
>
> (I tried to play with \ingnorespaces, \removeunwantedspaces and so but with no effect.)
>
> Best regards,
>
> Lukas
>
>
> --
> Ing. Lukáš Procházka | mailto:LPr@pontex.cz
> Pontex s. r. o.      | mailto:pontex@pontex.cz | http://www.pontex.cz | IDDS: nrpt3sn | IČO: 40763439
> Bezová 1658
> 147 14 Praha 4
>
> Mob.: +420 702 033 396___________________________________________________________________________________
> 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
> ___________________________________________________________________________________

Try the indentnext key. Either locally

\startitemize[][indentnext=no]

or, globally,

\setupitemize[
indentnext=no,
]

/Mikael
___________________________________________________________________________________
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
___________________________________________________________________________________

  reply	other threads:[~2019-04-11 10:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-11  8:01 Procházka Lukáš Ing.
2019-04-11 10:48 ` Mikael P. Sundqvist [this message]
2019-04-11 11:56   ` Procházka Lukáš Ing.
2019-04-11 12:44     ` Aditya Mahajan
2019-04-11 13:35       ` Procházka Lukáš Ing.
2019-04-11 19:43         ` Aditya Mahajan
2019-04-12  8:10           ` Procházka Lukáš Ing.

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='CAHy-LL8HRcNJ+QEbkZaTtotfae-GxsgNYRPCit1=yWShHfPKkA@mail.gmail.com' \
    --to=mickep@gmail.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).