From: Giuseppe Bilotta <gip.bilotta@iol.it>
Cc: ntg-context@ntg.nl
Subject: Re[3]: About itemize
Date: Tue, 12 Nov 2002 15:08:08 +0100 [thread overview]
Message-ID: <301726853.20021112150808@iol.it> (raw)
In-Reply-To: <5.1.0.14.1.20021112091240.02e2e0f0@server-1>
Tuesday, November 12, 2002 Hans Hagen wrote:
HH> At 12:46 AM 11/12/2002 +0100, you wrote:
>>Maybe we may want to have a per-startstop option
>>(obeypars=true,obeypars=false) together/in place of the global
>>\obeypars/\noobeypars (or \obeyparstrue/\obeyparsfalse).
>>
>>Let's say that the best thing (again IMO) is to have a global
>>option, overridable in each startstop: the obeypars key in
>>startstops would then accept the values true (force true), false
>>(force false), default (behave according to the global setting).
>>
>>Does this sound sensible?
HH> hm, tricky, in many cases start/stop can be anything, not just skips and so
Would it really be that tricky? It should just decide wether to
skip the next \par or not ...
HH> concerning redudancy: what's wrong with that? it gives you much more
HH> control and suits today's way of coding
Awfully verbose. Wrist-heavy. Definitely not the way to go (btw
that's the reason why I *hate* XML). It *requires* a tuned editor
which will insert the code for you, to reach the same productivity
level.
--
Giuseppe "Oblomov" Bilotta
next prev parent reply other threads:[~2002-11-12 14:08 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 ` Giuseppe Bilotta [this message]
2002-11-12 18:13 ` Re[3]: " 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=301726853.20021112150808@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).