From: Eric S Fraga <ucecesf@ucl.ac.uk>
To: Carsten Dominik <carsten.dominik@gmail.com>
Cc: emacs-orgmode@gnu.org, Karl Maihofer <ignoramus@gmx.de>,
Nicolas Goaziou <n.goaziou@gmail.com>
Subject: Re: Lists handling
Date: Sun, 28 Nov 2010 19:02:05 +0000 [thread overview]
Message-ID: <87zkst5l1u.fsf@ucl.ac.uk> (raw)
In-Reply-To: <4F78C3E7-6BC9-42EE-919E-A8B658D703BF@gmail.com> (Carsten Dominik's message of "Sun, 28 Nov 2010 14:59:15 +0100")
Carsten Dominik <carsten.dominik@gmail.com> writes:
> On Nov 27, 2010, at 7:12 PM, Nicolas Goaziou wrote:
>
>> Hello,
>>
>>>>>>> Karl Maihofer writes:
>>
>>> Thanks for that. Did you work on the demote/promote problem, too?
>>
>> No, nothing related to lists actually. But I added a way to configure
>> export of inline tasks.
>>
>>> As pointed out above in my special case inline tasks would be a
>>> great thing to have in lists. But I understand your reservation.
>>
>> It would be desirable to hear the opinions of others here.
>
> 1. My feeling is that it would be nice to allow drawers inside a list.
> 2. I don't think it is important to allow lists inside drawers inside
> lists - you can just say in the docs that this is not supported
> and let users deal with this limitation.
> 3. What should be allowed is to have lists inside a drawer that is not
> itself in a list. We need that for logbook entries and the like.
> 4. I also think that inline tasks inside a list are overkill and would
> overly complicate things.
Well, my immediate reaction was to jump in and say that this (pt 4) is
exactly when I most need inline tasks! My typical use case is taking
minutes at a meeting and assigning actions to individuals: inline tasks
are perfect for this.
However, on reflection, obviously a simple nested single item list would
do the job just fine *if* we could assign TODO actions to list
items... *but* we cannot unfortunately.
So, I'm back to needing to use inline tasks or putting in a request for
taskable list items...
Of course, this need could be because I don't actually understand
drawers and their potential for my particular use case. Any elucidation
on this aspect would be most welcome! For instance, could drawers give
me todo assignments?
thanks,
eric
--
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 23.2.1
: using Org-mode version 7.3 (release_7.3.148.gc3b7e)
next prev parent reply other threads:[~2010-11-28 19:02 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
[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 [this message]
[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=87zkst5l1u.fsf@ucl.ac.uk \
--to=ucecesf@ucl.ac.uk \
--cc=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=ignoramus@gmx.de \
--cc=n.goaziou@gmail.com \
/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).