From: Alan BRASLAU <alan.braslau@cea.fr>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: \startalignment
Date: Tue, 12 Jan 2016 11:07:15 -0700 [thread overview]
Message-ID: <20160112110715.34764b4a@cea.fr> (raw)
Hello,
Jean-Michel pointed out to me the following curiosity:
\starttext
\input tufte
\startalignment[middle]
\input ward
\stopalignment
\input tufte
\stoptext
The startalignment applies to the preceding text, too. Strange...
I never noticed this before as I have the habit of coding
\startalignment\stopalignment blocks set-off with leading and trailing
blank lines for better readability. But such practice could lead to
undesired results. Consider the following example:
\setupwhitespace [big]
\starttext
\input tufte
\startalignment[middle]
\input ward
\stopalignment
\input dawkins
\stoptext
So \stopalignment implicitly imposes a \par.
If I were to omit the blank line before \startalignment so that no big
whitespace be included before the centered block, the tufte text will
get middle aligned. Also, perhaps I might not wish for the dawkins text
to be separated by a big whitespace, logically as in:
\startparagraph
\input tufte
\startalignment [middle]
\input ward
\stopalignment
\input dawkins
\stopparagraph
Indeed, curious behavior.
Alan
___________________________________________________________________________________
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 reply other threads:[~2016-01-12 18:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-12 18:07 Alan BRASLAU [this message]
2016-01-12 18:29 ` \startalignment Wolfgang Schuster
2016-01-12 20:07 ` \startalignment Hans Hagen
2016-01-12 20:43 ` \startalignment Alan BRASLAU
2016-01-12 21:18 ` \startalignment 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=20160112110715.34764b4a@cea.fr \
--to=alan.braslau@cea.fr \
--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).