Received: from mail.proteosys.com ([62.225.9.49]) by nummer-3.proteosys with Microsoft SMTPSVC(5.0.2195.5329); Fri, 24 Jan 2003 20:48:43 +0100 Received: by mail.proteosys.com (8.12.2/8.12.2) with ESMTP id h0OJmf6C018280 for ; Fri, 24 Jan 2003 20:48:41 +0100 Received: from listserv.uni-heidelberg.de (listserv.uni-heidelberg.de [129.206.100.27]) by relay2.uni-heidelberg.de (8.12.4/8.12.4) with ESMTP id h0OJTAtt011766; Fri, 24 Jan 2003 20:29:10 +0100 (MET) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C2C3E1.997D9F80" Received: from listserv (listserv.uni-heidelberg.de [129.206.100.27]) by listserv.uni-heidelberg.de (8.12.2/8.12.2/SuSE Linux 0.6) with ESMTP id h0O3PCSl014696; Fri, 24 Jan 2003 20:21:54 +0100 Received: from LISTSERV.UNI-HEIDELBERG.DE by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8d) with spool id 9416 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Fri, 24 Jan 2003 20:21:54 +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.2/8.12.2/SuSE Linux 0.6) with ESMTP id h0OJLr5f022590 for ; Fri, 24 Jan 2003 20:21:53 +0100 Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.187]) by relay2.uni-heidelberg.de (8.12.4/8.12.4) with ESMTP id h0OJT8tt011754 for ; Fri, 24 Jan 2003 20:29:08 +0100 (MET) Received: from [212.227.126.162] (helo=mrelayng.kundenserver.de) by moutng.kundenserver.de with esmtp (Exim 3.35 #1) id 18c9Vk-0008Ra-00 for LATEX-L@listserv.uni-heidelberg.de; Fri, 24 Jan 2003 20:29:08 +0100 Received: from [80.129.7.224] (helo=istrati.mittelbach-online.de) by mrelayng.kundenserver.de with asmtp (Exim 3.35 #1) id 18c9Vk-0002zU-00 for LATEX-L@listserv.uni-heidelberg.de; Fri, 24 Jan 2003 20:29:08 +0100 Received: (from frank@localhost) by istrati.mittelbach-online.de (8.11.2/8.11.2/SuSE Linux 8.11.1-0.5) id h0OJSrs03490; Fri, 24 Jan 2003 20:28:53 +0100 In-Reply-To: References: Return-Path: X-Mailer: VM 6.96 under Emacs 20.7.1 X-OriginalArrivalTime: 24 Jan 2003 19:48:43.0506 (UTC) FILETIME=[99CAD520:01C2C3E1] 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: -2 () EMAIL_ATTRIBUTION,IN_REP_TO,REFERENCES,SPAM_PHRASE_03_05,X_AUTH_WARNING Content-class: urn:content-classes:message Subject: Re: [LATEX3] endless loop in xmarks with book class? Date: Fri, 24 Jan 2003 20:28:53 +0100 Message-ID: A<15921.37877.396653.396158@istrati.mittelbach-online.de> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Re: [LATEX3] endless loop in xmarks with book class? Thread-Index: AcLD4Znjt0qXUg7GQdyWKeKd9yjqUQ== From: "Frank Mittelbach" To: Reply-To: "Mailing list for the LaTeX3 project" Status: R X-Status: X-Keywords: X-UID: 4495 This is a multi-part message in MIME format. ------_=_NextPart_001_01C2C3E1.997D9F80 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Bjoern Pedersen writes: > I am currently doing some testing with the xor-package. > If I use book.cls, it goes in an inifite loop in the = mark-processing. > > If anybody has a fix, I would be interessted. \renewcommand\chaptermark[1]{} this is not a fix but a workaround. reason for the problem: xor uses multiple marks ie xmarks.dtx provides a different mark structure than std latex has. you can get into similar problems if you say in latex something like \mark{foo}, ie if you do not preserve the fact that current latex = requires a mark to consist of exactly 2 groups, eg \mark{{foo}{bar}} internally. now the mark mechanism for pagelayout hasn't been done so far, thus if = you combine the new OR with the old \pagestyle interface : "bomb*" \@tempa ->\q@no@value \q@no@value ->\q@no@value \q@no@value ->\q@no@value this is one of the famous "quarks" in the l3 experimental languages, it = allows for very tight loops :-) we always wondered if it would be too tight for use in a production = system. > A minimal test-file will follow during the weekend. fast, didn't know we had already weekend :-) cheers frank ------_=_NextPart_001_01C2C3E1.997D9F80 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: [LATEX3] endless loop in xmarks with book class?

Bjoern Pedersen writes:

 > I am currently doing some testing with the = xor-package.
 > If I use book.cls,  it goes in an = inifite loop in the mark-processing.
 >
 > If anybody has a fix, I would be = interessted.

\renewcommand\chaptermark[1]{}

this is not a fix but a workaround.


reason for the problem: xor uses multiple marks ie = xmarks.dtx provides a
different mark structure than std latex has.

you can get into similar problems if you say in latex = something like
\mark{foo}, ie if you do not preserve the fact that = current latex requires a
mark to consist of exactly 2 groups, eg = \mark{{foo}{bar}} internally.

now the mark mechanism for pagelayout hasn't been done = so far, thus if you
combine the new OR with the old \pagestyle interface = : "bomb*"


 \@tempa ->\q@no@value
 \q@no@value ->\q@no@value
 \q@no@value ->\q@no@value

this is one of the famous "quarks" in the l3 = experimental languages, it allows
for very tight loops :-)

we always wondered if it would be too tight for use in = a production system.



 > A minimal test-file will follow during the = weekend.

fast, didn't know we had already weekend :-)

cheers
frank

------_=_NextPart_001_01C2C3E1.997D9F80--