From: Hans Hagen <pragma@wxs.nl>
Subject: Re: About itemize
Date: Tue, 12 Nov 2002 00:33:40 +0100 [thread overview]
Message-ID: <5.1.0.14.1.20021112002309.031bcd80@remote-1> (raw)
In-Reply-To: <17719242809.20021111223129@iol.it>
At 10:31 PM 11/11/2002 +0100, you wrote:
>Monday, November 11, 2002 Idris S Hamid wrote:
>
>ISH> Dear posse,
>
>ISH> The itemize environment has a strange feature/bug:
>
>(This should answer your "quotation" question too, at least
>partly)
>
>All "blocks" have this bug; IIRC it comes from Hans preference of
>spacey "readable" sources; this means all \par tokens after a
>\stop are globbed, and (IIRC) a new paragraph is always started:
>thus the indentnext option *always* take place. IOW, you cannot
>have one of these blocks *within* a paragraph.
>
>Hans, am I right?
>
>Well, if I am, this is absolutely wrong. Presence or absence of
>\pars before and after should not be ignored, or at least should
>be made an option. My workaround for now is to use \nulls after
>\stop... commands, but this is somewhat clunky.
first of all, we're not dealing with a bug, it's a feature; so, if some
other behavior is wanted, it should be an option of extension to existing
mechanisms, nog a replacement.
there is one thing we should keep in mind: naive users are not always aware
of tex's empty line == par, so this is why \start/\stop things are
consistent in absense or presense of them;
distinguishing between display and semi-display is therefore not that
trivial, and the best option is separate environments, like
\startquotation ... \stopquotation
(or \startdquotation ... \stopdquotation for display quotation) versus
\startpquotation ... \stoppquotation
for an in-paragraph one (like we have with formulas, see core-mat.tex)
that way, one knows what to expect, since it's clear from the coding, and
not from a (forgotten, or accidental) empty line
another option is to have a dedidated environment
\startinparagraph ... \stopinparagraph
or \startcontinue ... \stopcontinue
which nills the surrounding whitespace and inhibits the next indent. (this
should be not that hard to implement)
Hans
-------------------------------------------------------------------------
Hans Hagen | PRAGMA ADE | pragma@wxs.nl
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------
information: http://www.pragma-ade.com/roadmap.pdf
documentation: http://www.pragma-ade.com/showcase.pdf
-------------------------------------------------------------------------
next prev parent reply other threads:[~2002-11-11 23:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-11 21:14 Idris S Hamid
2002-11-11 21:31 ` Giuseppe Bilotta
2002-11-11 23:33 ` Hans Hagen [this message]
2002-11-11 23:46 ` Re[2]: " Giuseppe Bilotta
2002-11-12 8:14 ` Hans Hagen
2002-11-12 14:08 ` Re[3]: " Giuseppe Bilotta
2002-11-12 18:13 ` Hans Hagen
2002-11-12 22:12 ` Re[4]: " Giuseppe Bilotta
2002-11-13 8:40 ` Hans Hagen
2002-11-13 11:32 ` Re[5]: " Giuseppe Bilotta
2002-11-14 2:54 ` Idris S Hamid
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=5.1.0.14.1.20021112002309.031bcd80@remote-1 \
--to=pragma@wxs.nl \
--cc=ntg-context@ref.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).