From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Karl Maihofer <ignoramus@gmx.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: Lists handling
Date: Sat, 27 Nov 2010 00:51:57 +0100 [thread overview]
Message-ID: <87wrnzhcde.wl%n.goaziou@gmail.com> (raw)
In-Reply-To: <20101126191600.17972vn4jdlkdm68@webmail.df.eu>
Hello,
>>>>> Karl Maihofer writes:
> These documents must be updated and will be exported to HTML
> regularly. Some documents have 500+ pages and many many of these
> "inline task" notes.
Wouldn't drawers be more appropriate here than inline tasks? Not that
it would work with a drawer either, but the examples given seem to
focus more on content than on a task title.
> My problem isn't only that the exporter does not recognize this
> structure as one single list anymore (otherwise I could use an old
> Org version) but also that indentation does not work. Nicolas
> mentioned this already and I think this was one of the reasons for
> changing the handling of lists.
I don't understand what the indentation problem you're talking about
is, but I worked on indentation wrt inline tasks recently. My work is
at:
git://github.com/ngz/org-mode-lists.git inlinetask
It might solve some of your problems.
> Does anybody see a chance to make Org recognize such "interrupted"
> lists as one list and make indentation and export to HTML work
> properly?
I'm writing down ideas to put in a future update of lists. Some
previously "unsupported anymore" stuff may appear again, after a phase
of testing on a parallel git branch.
In this context, you raise an interesting question about inline tasks.
I have my idea (read below), but a discussion about it might be
productive.
> Wouldn't it be possible to tell Org to recognize text or inline
> tasks right behind a bullet point (next line) as belonging to this
> bullet point so that Org can treat the next bullet point as part of
> the same list?
It looks to me the syntax is way too subtle to be clear. Moreover,
lists are all about indentation, and inline tasks defeat that as they
live at column 0. They also visually break any structure around.
To be honest, I'm not very enthusiastic about allowing inline tasks
within lists. On the other hand, I will definitely let drawers in,
thus my first question.
Regards,
-- Nicolas
next prev parent reply other threads:[~2010-11-26 23:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-26 18:16 Lists handling Karl Maihofer
2010-11-26 23:51 ` Nicolas Goaziou [this message]
[not found] ` <28320_1290815524_oAQNq442028994_87wrnzhcde.wl%n.goaziou@gmail.com>
2010-11-27 11:47 ` Karl Maihofer
2010-11-27 18:12 ` Nicolas Goaziou
2010-11-28 13:59 ` Carsten Dominik
2010-11-28 19:02 ` Eric S Fraga
[not found] ` <14003_1290970935_oASJ2FXi018046_87zkst5l1u.fsf@ucl.ac.uk>
2010-11-28 20:08 ` Karl Maihofer
[not found] ` <5367_1290881529_oARIC8fA005869_87vd3ihc0d.wl%n.goaziou@gmail.com>
2010-11-28 11:55 ` Karl Maihofer
2010-11-28 12:12 ` Nicolas Goaziou
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=87wrnzhcde.wl%n.goaziou@gmail.com \
--to=n.goaziou@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=ignoramus@gmx.de \
/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).