From: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Difference between texexec and context when using indent
Date: Sun, 17 Apr 2011 11:07:48 +0200 [thread overview]
Message-ID: <EEB7AB8F-DF94-4D62-9B72-ED752057D24D@googlemail.com> (raw)
In-Reply-To: <BANLkTimTohEXN6EhajG8P24SmN1Mr305WA@mail.gmail.com>
Am 15.04.2011 um 14:11 schrieb Cecil Westerhof:
> With the following code:
> \setupindenting[yes,medium,next]
>
> \starttext
>
> \input knuth
>
> \blank
>
> \input knuth
>
> \stoptext
>
> When using texexec (MKII) the paragraph after the \blank is not
> indented. When using context (MKIV) it is. Why this difference?
And you think it’s better to let \blank behave different dependent
on the indenting settings?
% engine=pdftex
\starttext
\setupindenting[yes,medium,first]
\input knuth
\blank
\input knuth
\page
\setupindenting[yes,medium,next]
\input knuth
\blank
\input knuth
\stoptext
To control whether the next paragraph is indented or not should
better be controlled with by \setupblank and not from \setupindenting.
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
___________________________________________________________________________________
next prev parent reply other threads:[~2011-04-17 9:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-15 12:11 Cecil Westerhof
2011-04-17 9:07 ` Wolfgang Schuster [this message]
2011-04-18 7:24 ` Cecil Westerhof
2011-04-18 13:46 ` Wolfgang Schuster
2011-04-18 15:13 ` 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=EEB7AB8F-DF94-4D62-9B72-ED752057D24D@googlemail.com \
--to=schuster.wolfgang@googlemail.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).