From: Taco Hoekwater <taco@elvenkind.com>
Subject: Re: environment files and indenting
Date: Tue, 08 Aug 2006 19:46:26 +0200 [thread overview]
Message-ID: <44D8CDF2.7070206@elvenkind.com> (raw)
In-Reply-To: <E1GAUMv-0003Si-00@skye.ra.phy.cam.ac.uk>
Sanjoy Mahajan wrote:
>>The overfull box is caused by a strut. It is easily removed by
>> \def\verticalstrut{\normalvbox {\hsize \zeropoint \noindent\strut }}
>
>
> Easily removed, but not so easily found! Thanks, that fixes it.
> Looking at the standard definition of \verticalstrut (in
> core-spa.tex):
>
> \def\verticalstrut {\normalvbox{\hsize\zeropoint\strut}}
>
> your fix adds a \noindent. Is that a general solution (e.g. for a
> subsequent release) or does it have side effects?
The release I just announced fixes the problem by using \forgetall
instead of \noindent. Side-effect do not matter because any effects
will stay local to the \normalvbox, and that is left right away.
Cheers, Taco
prev parent reply other threads:[~2006-08-08 17:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-07 18:55 Sanjoy Mahajan
2006-08-08 9:33 ` Taco Hoekwater
2006-08-08 11:53 ` Sanjoy Mahajan
2006-08-08 13:21 ` Taco Hoekwater
2006-08-08 16:23 ` Sanjoy Mahajan
2006-08-08 17:46 ` Taco Hoekwater [this message]
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=44D8CDF2.7070206@elvenkind.com \
--to=taco@elvenkind.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).