Received: from mail.proteosys.com ([62.225.9.49]) by nummer-3.proteosys with Microsoft SMTPSVC(5.0.2195.5329); Wed, 12 Mar 2003 00:54:01 +0100 Received: by mail.proteosys.com (8.12.3/8.12.2) with ESMTP id h2BNrxa9023784 for ; Wed, 12 Mar 2003 00:54:00 +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 h2BNl0le009968; Wed, 12 Mar 2003 00:47:00 +0100 (MET) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C2E829.7D1AB280" 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 h2BN04Ne001677; Wed, 12 Mar 2003 00:46:40 +0100 Received: from LISTSERV.UNI-HEIDELBERG.DE by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8d) with spool id 6493 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Wed, 12 Mar 2003 00:46:40 +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 h2BNkeMK002161 for ; Wed, 12 Mar 2003 00:46:40 +0100 Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.187]) by relay2.uni-heidelberg.de (8.12.8/8.12.8) with ESMTP id h2BNkwle009962 for ; Wed, 12 Mar 2003 00:46:58 +0100 (MET) Received: from [212.227.126.162] (helo=mrelayng.kundenserver.de) by moutng.kundenserver.de with esmtp (Exim 3.35 #1) id 18stSU-0002F5-00 for LATEX-L@listserv.uni-heidelberg.de; Wed, 12 Mar 2003 00:46:58 +0100 Received: from [80.129.3.92] (helo=istrati.mittelbach-online.de) by mrelayng.kundenserver.de with asmtp (TLSv1:EDH-RSA-DES-CBC3-SHA:168) (Exim 3.35 #1) id 18stST-0005D5-00 for LATEX-L@listserv.uni-heidelberg.de; Wed, 12 Mar 2003 00:46:58 +0100 Received: (from frank@localhost) by istrati.mittelbach-online.de (8.11.2/8.11.2/SuSE Linux 8.11.1-0.5) id h2BNjbl19882; Wed, 12 Mar 2003 00:45:37 +0100 In-Reply-To: <15982.27950.882763.502473@fell.open.ac.uk> References: <630BE70C8320D6118D240002A589ABB204A95102@DERUM201> <15982.27950.882763.502473@fell.open.ac.uk> Return-Path: X-Mailer: VM 6.96 under Emacs 20.7.1 X-OriginalArrivalTime: 11 Mar 2003 23:54:02.0254 (UTC) FILETIME=[7DDA0AE0:01C2E829] X-Authentication-Warning: istrati.mittelbach-online.de: frank set sender to frank@mittelbach-online.de using -f X-Scanned-By: MIMEDefang 2.28 (www . roaringpenguin . com / mimedefang) X-Spam-Score: -0.7 () IN_REP_TO,REFERENCES,SPAM_PHRASE_02_03,X_AUTH_WARNING Content-class: urn:content-classes:message Subject: Re: algorithm for \addvspace Date: Wed, 12 Mar 2003 00:45:37 +0100 Message-ID: A<15982.29985.78665.694047@istrati.mittelbach-online.de> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Re: algorithm for \addvspace Thread-Index: AcLoKX4BgtVLW/q8ROGM1A/oYpzLDg== From: "Frank Mittelbach" To: Reply-To: "Mailing list for the LaTeX3 project" Status: R X-Status: X-Keywords: X-UID: 4573 This is a multi-part message in MIME format. ------_=_NextPart_001_01C2E829.7D1AB280 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Chris Rowley writes: > Frank, Lars > > Take care! > > I have not followed all the details of your debate but I get the = impression > that you may be wrong about how \vspace interacts with \addvspace. oops, indeed. but fortunately it doesn't actually make that particular = problem go away it only makes more prominent, eg \addvspace{8pt} \addvspace{10pt} gives 10pt of space while \addvspace{8pt} \vspace{2pt} \addvspace{10pt} 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. so i'm would not call this: > This is best described as `no interaction', since \vspace and > relatives all `end with' > > \vskip\z@skip . it is more "kill interaction" and that was the problem i pointed out. thus i would say its purpose is not so clear rather than: > > 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" right? frank ------_=_NextPart_001_01C2E829.7D1AB280 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: algorithm for \addvspace

Chris Rowley writes:
 > Frank, Lars
 >
 > Take care!
 >
 > I have not followed all the details of = your debate but I get the impression
 > that you may be wrong about how \vspace = interacts with \addvspace.

oops, indeed. but fortunately it doesn't actually make = that particular problem
go away it only makes more prominent, eg

\addvspace{8pt}
\addvspace{10pt}

gives 10pt of space while

\addvspace{8pt}
\vspace{2pt}
\addvspace{10pt}

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.

so i'm would not call this:

 > This is best described as `no interaction', = since \vspace and
 > relatives all `end with'
 >
 >   \vskip\z@skip .

it is more "kill interaction" and that was = the problem i pointed out.

thus i would say its purpose is not so clear rather = than:
 >
 > 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"

right?

frank

------_=_NextPart_001_01C2E829.7D1AB280--