From: Giuseppe Bilotta <gip.bilotta@iol.it>
Cc: ntg-context@ntg.nl
Subject: Re[4]: About itemize
Date: Tue, 12 Nov 2002 23:12:25 +0100 [thread overview]
Message-ID: <1862726500.20021112231225@iol.it> (raw)
In-Reply-To: <5.1.0.14.1.20021112191244.03360dc8@server-1>
Tuesday, November 12, 2002 Hans Hagen wrote:
>>Would it really be that tricky? It should just decide wether to
>>skip the next \par or not ...
HH> well, the point is that no command, except fr sectioning and index commands
HH> look ahead, so what excactly do you mean with 'skip the next par'?
Uhm. Ok, let's get at it slowly. I don't know how it works
internally, but regadless of this, the behaviour seems to be the
same regardless of wether I leave an empty line after the \stop,
or not (and also before the \start, or not). Do \starts and \stops
automatically force a new paragraph all the time?
--
Giuseppe "Oblomov" Bilotta
next prev parent reply other threads:[~2002-11-12 22:12 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
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 ` Giuseppe Bilotta [this message]
2002-11-13 8:40 ` Re[4]: " 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=1862726500.20021112231225@iol.it \
--to=gip.bilotta@iol.it \
--cc=ntg-context@ntg.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).