From: "William Henney" <whenney@gmail.com>
To: Eddward DeVilla <eddward@gmail.com>
Cc: emacs-orgmode@gnu.org, cezar <cezar@mixandgo.ro>
Subject: Re: Re: list indentation
Date: Sat, 9 Feb 2008 19:09:29 -0600 [thread overview]
Message-ID: <41c818190802091709r68e36eeq1e42df06c6d8673c@mail.gmail.com> (raw)
In-Reply-To: <b71b18520802091526n4d204a08g320313a7a0e20e6d@mail.gmail.com>
Hi Eddward
On Feb 9, 2008 5:26 PM, Eddward DeVilla <eddward@gmail.com> wrote:
> On Feb 9, 2008 4:50 PM, William Henney <whenney@gmail.com> wrote:
> > You are right, though, that it is the end-of-list marker that is
> > important. On reflection, it seems to me that a beginning-of-list
> > marker is not necessary.
>
> That's why I suggested -----. It's really only needed as a
> terminator, but I like symmetry. I'd like to be able have something
> at the top, but it should not be required.
But it causes problems to allow the same marker to be used at the
start and end. For instance, consider the following:
-----
- item one
- item two
----- <- point is on this line
When I hit TAB, how is org to know whether the "-----" is supposed to
start a new sublist (and so should be indented 3 spaces) or is meant
to end the preceding list (and so should not be indented)?
That is why I proposed that IF we are to have both start and end
markers, THEN they need to be distinct. However, I now think that it
would be better to just have end markers. Personally, I would prefer
"-/" for the XMLish feel. My objections to "-----" are
1. It is hard to remember (was it 5 dashes or 4?)
2. It is a pain to type when you have the "tex" input method turned on
3. It conflicts with existing usage (sec 12.6.5 of the manual)
* A line consisting of only dashes, and at least 5 of them, will be
exported as a horizontal line (`<hr/>' in HTML).
> Really, the terminator
> should not be required unless you need it to tell org to end the list,
> so we don't break current files.
>
Agreed.
Cheers
Will
--
Dr William Henney, Centro de Radioastronomía y Astrofísica,
Universidad Nacional Autónoma de México, Campus Morelia
next prev parent reply other threads:[~2008-02-10 1:09 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-07 18:58 list indentation cezar
2008-02-07 23:31 ` Hugo Schmitt
2008-02-08 9:24 ` Carsten Dominik
2008-02-09 0:29 ` cezar
2008-02-09 7:17 ` Carsten Dominik
2008-02-09 7:26 ` cezar
2008-02-09 17:02 ` Eddward DeVilla
2008-02-09 21:45 ` William Henney
2008-02-09 22:17 ` cezar
2008-02-09 22:50 ` William Henney
2008-02-09 23:26 ` Eddward DeVilla
2008-02-10 1:09 ` William Henney [this message]
2008-02-10 3:55 ` Eddward DeVilla
2008-02-10 4:47 ` William Henney
2008-02-10 5:05 ` Eddward DeVilla
2008-02-10 7:29 ` Carsten Dominik
2008-02-10 8:00 ` cezar
2008-02-10 10:58 ` Carsten Dominik
2008-02-10 19:26 ` cezar
2008-02-09 23:41 ` cezar
2008-02-10 1:28 ` William Henney
2008-02-10 1:33 ` Cezar Halmagean
2008-02-10 1:35 ` William Henney
2008-02-10 20:42 ` Bastien Guerry
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=41c818190802091709r68e36eeq1e42df06c6d8673c@mail.gmail.com \
--to=whenney@gmail.com \
--cc=cezar@mixandgo.ro \
--cc=eddward@gmail.com \
--cc=emacs-orgmode@gnu.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).