Received: from mail.proteosys.com ([62.225.9.49]) by nummer-3.proteosys with Microsoft SMTPSVC(5.0.2195.5329); Wed, 12 Mar 2003 08:45:27 +0100 Received: by mail.proteosys.com (8.12.3/8.12.2) with ESMTP id h2C7jPa9024572 for ; Wed, 12 Mar 2003 08:45:25 +0100 Received: from listserv.uni-heidelberg.de (listserv.uni-heidelberg.de [129.206.100.27]) by relay2.uni-heidelberg.de (8.12.8/8.12.8) with ESMTP id h2C7dwle010913; Wed, 12 Mar 2003 08:39:58 +0100 (MET) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C2E86B.58DFC580" Received: from listserv (listserv.uni-heidelberg.de [129.206.100.27]) by listserv.uni-heidelberg.de (8.12.3/8.12.3/SuSE Linux 0.6) with ESMTP id h2BN04Qo001677; Wed, 12 Mar 2003 08:38:13 +0100 Received: from LISTSERV.UNI-HEIDELBERG.DE by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8d) with spool id 6750 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Wed, 12 Mar 2003 08:38:13 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.5 Received: from relay2.uni-heidelberg.de (relay2.uni-heidelberg.de [129.206.210.211]) by listserv.uni-heidelberg.de (8.12.3/8.12.3/SuSE Linux 0.6) with ESMTP id h2C7cDMK005659 for ; Wed, 12 Mar 2003 08:38:13 +0100 Received: from mutant.triumf.ca (mutant.Triumf.CA [142.90.112.22]) by relay2.uni-heidelberg.de (8.12.8/8.12.8) with ESMTP id h2C7cVle010573 for ; Wed, 12 Mar 2003 08:38:32 +0100 (MET) Received: (from asnd@localhost) by mutant.triumf.ca (8.9.3/8.9.3) id XAA12301; Tue, 11 Mar 2003 23:41:09 -0800 In-Reply-To: Frank Mittelbach's message of "Wed, 12 Mar 2003 00:45:37 +0100" Lines: 29 Organization: TRIUMF: Canada's national meson facility References: <630BE70C8320D6118D240002A589ABB204A95102@DERUM201> <15982.27950.882763.502473@fell.open.ac.uk> <15982.29985.78665.694047@istrati.mittelbach-online.de> Return-Path: X-OriginalArrivalTime: 12 Mar 2003 07:45:28.0654 (UTC) FILETIME=[59DC26E0:01C2E86B] User-Agent: Gnus/5.0807 (Gnus v5.8.7) Emacs/20.7 X-Authentication-Warning: mutant.triumf.ca: asnd set sender to asnd@triumf.ca using -f X-Scanned-By: MIMEDefang 2.28 (www . roaringpenguin . com / mimedefang) X-Spam-Score: -4.8 () EMAIL_ATTRIBUTION,IN_REP_TO,NOSPAM_INC,QUOTED_EMAIL_TEXT,REFERENCES,SPAM_PHRASE_00_01,USER_AGENT,USER_AGENT_GNUS_UA,X_AUTH_WARNING Content-class: urn:content-classes:message Subject: Re: algorithm for \addvspace Date: Wed, 12 Mar 2003 08:41:09 +0100 Message-ID: A X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Re: algorithm for \addvspace Thread-Index: AcLoa1oCfk4lNnFbRsy+rT6EDFllZg== From: "Donald Arseneau" To: Reply-To: "Mailing list for the LaTeX3 project" Status: R X-Status: X-Keywords: X-UID: 4574 This is a multi-part message in MIME format. ------_=_NextPart_001_01C2E86B.58DFC580 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Frank Mittelbach writes: > give 20pt not 18pt as i claimed. and it is still not clear for the = user what > value to use in \vspace to get say 2pt more space without knowing the = actual > values in the \addvspace commands that have been used internally. I've looked at \addvspace in the past, but haven't had the time to look at it during this thread. The matter of inserting \vspace in between two \addvspace has been discussed before; I just don't recall where. I think it is quite consistent that \vspace interrupts the merging of \addvspace, just like everything else does, including the (in)famous color commands. > > The purpose of this is that, in LaTeX, _only_ those spaces > > added by \addvspace should interact (and with \addpenalty); > > all other spaces are irrelevant. > > since an extra space via \vspace is fairly "relevant" That's just the way they've always been, and it is the original intent. Consecutive \addvspace will merge; \vspace add. Yes it is a misnomer. (Don't read this as disagreeing with anything stated; I'm just throwing out some thoughts.) Donald Arseneau asnd@triumf.ca ------_=_NextPart_001_01C2E86B.58DFC580 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: algorithm for \addvspace

Frank Mittelbach = <frank.mittelbach@LATEX-PROJECT.ORG> writes:

> give 20pt not 18pt as i claimed. and it is still = not clear for the user what
> value to use in \vspace to get say 2pt more = space without knowing the actual
> values in the \addvspace commands that have been = used internally.

I've looked at \addvspace in the past, but haven't had = the time
to look at it during this thread.  The matter of = inserting
\vspace in between two \addvspace has been discussed = before;
I just don't recall where.

I think it is quite consistent that \vspace interrupts = the
merging of \addvspace, just like everything else = does, including
the (in)famous color commands.

>  > The purpose of this is that, in LaTeX, = _only_ those spaces
>  > added by \addvspace should interact = (and with \addpenalty);
>  > all other spaces are = irrelevant.
>
> since an extra space via \vspace is fairly = "relevant"

That's just the way they've always been, and it is the = original
intent.  Consecutive \addvspace will merge; = \vspace add.  Yes it
is a misnomer.

(Don't read this as disagreeing with anything stated; = I'm just
throwing out some thoughts.)

Donald = Arseneau           = ;            =    asnd@triumf.ca

------_=_NextPart_001_01C2E86B.58DFC580--