From: Sanjoy Mahajan <sanjoy@mrao.cam.ac.uk>
Subject: Re: Two misfeatures in placefigure
Date: Wed, 25 Oct 2006 13:57:32 +0100 [thread overview]
Message-ID: <E1GciK4-0007bT-00@skye.ra.phy.cam.ac.uk> (raw)
In-Reply-To: Your message of "Wed, 25 Oct 2006 14:10:43 +0200." <453F5443.3060605@wxs.nl>
> >> 2) The paragraph after the figure is indented, even if it comes right
> >> after a \section.
<wild speculation>
Thinking about how I prevented such parindents in my plain TeX days,
by using \ignorespaces\noindent in the definition of \section. If
that's what ConTeXt does, perhaps the \placefigure code inserts a
spurious space, which normally doesn't show up because it's inserted
in vertical mode, but it is enough to confuse the \ignorespaces?
</wild speculation>
-Sanjoy
`Never underestimate the evil of which men of power are capable.'
--Bertrand Russell, _War Crimes in Vietnam_, chapter 1.
next prev parent reply other threads:[~2006-10-25 12:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-25 1:38 Aditya Mahajan
2006-10-25 9:20 ` Taco Hoekwater
2006-10-25 12:10 ` Hans Hagen
2006-10-25 12:57 ` Sanjoy Mahajan [this message]
2006-10-25 14:00 ` Aditya Mahajan
2006-10-25 19:11 ` Peter Münster
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=E1GciK4-0007bT-00@skye.ra.phy.cam.ac.uk \
--to=sanjoy@mrao.cam.ac.uk \
--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).