The attached text is a first draft of a proposed extension to the
Description field to explicitly handle bulleted lists. The extended
syntax allows list items to be treated specially by frontends (for
instance, bullet characters can be replaced with graphics, and the
body of the list item can
On Mon, Dec 12, 2005 at 03:09:52PM -0800, Daniel Burrows wrote:
The attached text is a first draft of a proposed extension to the
Description field to explicitly handle bulleted lists. The extended
wow! that's quite a document. i'm glad to see that people are
focusing on the Really Big
[Daniel Burrows]
(1) The first line begins with N 2 spaces,
Don't you mean N = 2?
(2) The first non-space character of the first line is a bullet
character, and
(3) Each subsequent line begins with at least N + 1 + M spaces,
where M is the number of spaces immediately
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel Burrows [EMAIL PROTECTED] writes:
The attached text is a first draft of a proposed extension to the
Description field to explicitly handle bulleted lists.
That's quite a complex document for something I believe should be
quite simple.
On Mon, Dec 12, 2005 at 06:38:59PM -0500, sean finney [EMAIL PROTECTED] was
heard to say:
On Mon, Dec 12, 2005 at 03:09:52PM -0800, Daniel Burrows wrote:
The attached text is a first draft of a proposed extension to the
Description field to explicitly handle bulleted lists. The extended
On Mon, Dec 12, 2005 at 03:09:52PM -0800, Daniel Burrows wrote:
The attached text is a first draft of a proposed extension to the
Description field to explicitly handle bulleted lists. The extended
syntax allows list items to be treated specially by frontends (for
instance, bullet
On Mon, Dec 12, 2005 at 05:49:02PM -0600, Peter Samuelson [EMAIL PROTECTED]
was heard to say:
[Daniel Burrows]
(1) The first line begins with N 2 spaces,
Don't you mean N = 2?
(2) The first non-space character of the first line is a bullet
character, and
(3) Each
On Tue, Dec 13, 2005 at 12:01:52AM +, Roger Leigh [EMAIL PROTECTED] was
heard to say:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel Burrows [EMAIL PROTECTED] writes:
The attached text is a first draft of a proposed extension to the
Description field to explicitly handle
On Tue, Dec 13, 2005 at 01:21:41AM +0100, Jeroen van Wolffelaar [EMAIL
PROTECTED] was heard to say:
On Mon, Dec 12, 2005 at 03:09:52PM -0800, Daniel Burrows wrote:
Extensions to the syntax of Description blocks:
As mentioned above, all lines beginning with two or more spaces are
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel Burrows [EMAIL PROTECTED] writes:
On Tue, Dec 13, 2005 at 12:01:52AM +, Roger Leigh [EMAIL PROTECTED] was
heard to say:
Daniel Burrows [EMAIL PROTECTED] writes:
The attached text is a first draft of a proposed extension to the
[Daniel Burrows]
(1) The first line begins with N = 2 spaces,
(3) Each subsequent line begins with at least N + 2 spaces.
Hm. That brings up the minor point of whether N should ever be
anything but (2 * nest_level).
I don't feel strongly about that one, though.
Also, in the Best
[Peter Samuelson]
Hm. That brings up the minor point of whether N should ever be
anything but (2 * nest_level).
Or if you consider nest_level to be zero-based, (2 + 2 * nest_level).
It occurs to me, though, that some might prefer the raw presentation
look of (2 + 3 * nest_level). I might
12 matches
Mail list logo
