From: Hans Hagen <pragma@wxs.nl>
Subject: Re[6]: In-paragraph display
Date: Tue, 03 Dec 2002 13:48:32 +0100 [thread overview]
Message-ID: <5.1.0.14.1.20021203134547.02556be0@server-1> (raw)
In-Reply-To: <1547767058.20021203121258@iol.it>
At 12:12 PM 12/3/2002 +0100, you wrote:
>Tuesday, December 3, 2002 Hans Hagen wrote:
>
>HH> now, say that there will be:
>
>HH> (1) quotation
>HH> (2) blockquotation
>
>HH> with
>
>HH> (1) forcing a new par
>HH> (2) behaving the way you want
>
>HH> and both can be set up as usual to act differently, that would solve the
>HH> problem, wouldn't it, since you could either setup up quotation
>differently
>HH> or use blockquotation. (i'm not going to change the quotation defaults,
>HH> simply because it would break compatibility)
>
>That's fine for me. But wow would this differ from having the
>possibility to set quotation (and other displayed environments) to
>not force new paragraphs? After all, a blockquotation can easily
>be tuned to force new paragraphs (just but before=\par and
>after=\par), but the converse is not true.
well, if before=\blank, that will not change; actually, quotations are
hooked into narrower, which start/ends new pars; a more generic switch can
be built in, but takes time, so in due time you can have that switch (with
of course the danger that nothing generates a par anymore, or worse, that
anybody disagrees with any defaults), but not in a quick and dirty hack; i
will first make a proper startdisplay/stopdisplay, and after that it may go
in some env's
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-12-03 12:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-01 9:06 Giuseppe Bilotta
2002-12-02 14:34 ` Hans Hagen
2002-12-02 17:03 ` Re[2]: " Giuseppe Bilotta
2002-12-02 17:40 ` Hans Hagen
2002-12-03 0:37 ` Re[3]: " Giuseppe Bilotta
2002-12-03 1:18 ` Bruce D'Arcus
2002-12-03 9:25 ` Re[5]: " Giuseppe Bilotta
2002-12-03 10:46 ` Hans Hagen
2002-12-03 11:12 ` Re[6]: " Giuseppe Bilotta
2002-12-03 12:48 ` Hans Hagen [this message]
2002-12-03 15:24 ` Re[7]: " Giuseppe Bilotta
2002-12-03 19:47 ` Re[3]: " Simon Pepping
2002-12-03 11:00 ` Hans Hagen
2002-12-03 15:24 ` Re[4]: " Giuseppe Bilotta
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.20021203134547.02556be0@server-1 \
--to=pragma@wxs.nl \
--cc=ntg-context@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).