Received: by nummer-3.proteosys id <01C19443.4A407C0C@nummer-3.proteosys>; Thu, 3 Jan 2002 11:42:07 +0100 MIME-Version: 1.0 x-vm-v5-data: ([nil nil nil nil nil nil nil t nil][nil nil nil nil nil nil nil nil nil nil nil nil nil nil nil nil]) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C19443.4A407C0C" X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message Subject: Interrupted lists Date: Wed, 23 Oct 1991 01:00:00 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: Sender: "LaTeX-L Mailing list" To: "Rainer M. Schoepf" Reply-To: "LaTeX-L Mailing list" Status: R X-Status: X-Keywords: X-UID: 415 This is a multi-part message in MIME format. ------_=_NextPart_001_01C19443.4A407C0C Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Last weekend I read through David Rhead's scribblings on LaTeX structure, and somewhere there was something about interrupted lists. Let me tell you how I've solved that in a structurally totally unacceptable, but rather effective way. In my Lollipop format there is a list of indents that controls everything (lists, displays, et cetera) that doesn't have its own explicit indentation control. After an insightful moment I decided to implement commands \PopListLevel and \PushListLevel that simply de/increase the \lefskip to the previous/next level. Of course you should only use them in a group, but that's simple. These commands can be used by the user to interrupt a list, or can be incorporated in macros in a format. In fact, the latter = possibility is what I needed. I doubt that it interests anyone (let's face it, when I claimed the other day to have solved the problem of fragile macros the response was zilch), but I'm going to tell you anyway why: in Lollipop as it stood a few months ago it took the style designer one line to declare that a 'list of definitions' or whatever external file should exist, it took a few lines in the definition of \definition to determine what exactly should be written to that file. The problem = was how to specify how the 'list of whatevers' file should be typeset. The problem with (say) a table of contents is that it looks like a list, but it is hard to control the jumping between levels. I still think it was a brilliant idea to make every item into a separate list of one item. With \PushListlevel every item can then place itself on the appropriate indentation. Example: in the table of contents \Chapter does nothing, \section does one \PushListLevel, and \subsection does two of them. Neat or what? Victor Eijkhout Center for Supercomputing Research and Development University of Illinois at Urbana-Champaign 305 Talbot Laboratory phone: +1 217 244-0047 (office) 104 South Wright Street +1 217 356-0876 (home) Urbana, Illinois 61801-2932, USA fax: +1 217 244-1351 home: 2503 W. Springfield Av, Apt. K-4, Champaign 61821, USA ------_=_NextPart_001_01C19443.4A407C0C Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Interrupted lists

Last weekend I read through David Rhead's scribblings = on LaTeX
structure, and somewhere there was something about = interrupted
lists. Let me tell you how I've solved that in a = structurally
totally unacceptable, but rather effective = way.

In my Lollipop format there is a list of indents that = controls
everything (lists, displays, et cetera) that doesn't = have its
own explicit indentation control. After an insightful = moment
I decided to implement commands \PopListLevel and = \PushListLevel
that simply de/increase the \lefskip to the = previous/next level.

Of course you should only use them in a group, but = that's simple.

These commands can be used by the user to interrupt a = list,
or can be incorporated in macros in a format. In = fact, the latter possibility
is what I needed. I doubt that it interests anyone = (let's face it,
when I claimed the other day to have solved the = problem of fragile
macros the response was zilch), but I'm going to tell = you anyway why:
in Lollipop as it stood a few months ago it took the = style designer
one line to declare that a 'list of definitions' or = whatever external
file should exist, it took a few lines in the = definition of \definition
to determine what exactly should be written to that = file. The problem was
how to specify how the 'list of whatevers' file = should be typeset.

The problem with (say) a table of contents is that it = looks like a list,
but it is hard to control the jumping between = levels.
I still think it was a brilliant idea to make every = item into a
separate list of one item. With \PushListlevel every = item can then
place itself on the appropriate indentation.
 Example: in the table of contents \Chapter does = nothing, \section does
one \PushListLevel, and \subsection does two of = them.

Neat or what?

Victor Eijkhout
 Center for Supercomputing Research and = Development
 University of Illinois at = Urbana-Champaign
 305 Talbot = Laboratory          &nb= sp;      phone: +1 217 244-0047 (office)
 104 South Wright = Street           &= nbsp;          +1 217 = 356-0876 (home)
 Urbana, Illinois 61801-2932, = USA        fax: +1 217 = 244-1351

home: 2503 W. Springfield Av, Apt. K-4, Champaign = 61821, USA


------_=_NextPart_001_01C19443.4A407C0C--