emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Karl Maihofer <ignoramus@gmx.de>
To: Eric S Fraga <ucecesf@ucl.ac.uk>
Cc: emacs-orgmode@gnu.org, Nicolas Goaziou <n.goaziou@gmail.com>,
	Carsten Dominik <carsten.dominik@gmail.com>
Subject: Re: Lists handling
Date: Sun, 28 Nov 2010 21:08:10 +0100	[thread overview]
Message-ID: <20101128210810.11245oaxpb4k74gs@webmail.df.eu> (raw)
In-Reply-To: <14003_1290970935_oASJ2FXi018046_87zkst5l1u.fsf@ucl.ac.uk>


Eric S Fraga <ucecesf@ucl.ac.uk> schrieb:
> 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...

Seems as if I'm not alone. :-)

1) I understand that inline tasks withhin lists are not the perfect
    solution. They break the list visually because they live in column 1.
    So if you do not need to define a real task but just write a comment,
    a drawer should be the better solution.

,----
| - Item 1
|   - Item 1a
|     :COMMENT:
|     This is a comment.
|     :END:
|   - Item 1b
| - Item 2
| - Item 3
`----

2) Another topic is the need of real tasks withhin lists. And I think that
    this depends on how you use Org. If you use Org just to write down
    thoughts using headings, you can define tasks for any item.

,----
| * Text
| * Text
| ** Text
| ** TODO Text
| * Text
`----

But if you have more complex documents that have different headings and
you'd like to have a list view for your structured thoughts, you may
prefer lists. And when these lists get larger, the need to define list items
as tasks gets more important.

Since Org is based on a outline structure of items beginning with a star,
it may be difficult to realise the possibility to mark list items as tasks!?

,----
| - Item 1
|   - Item 1a
|   - TODO Item 1b
| - Item 3
`----

So inline tasks may be a work around. My first guess was something like that:

,----
| - Item 1
|   - Item 1a
| *************** TODO Inline Task
| Here is text.
| *************** END
|   - Item 1b
| - Item 2
| - Item 3
`----

If that is difficult to implement and drawers are a appropriate way
to mark text to belong to a list item, what about using inline tasks
withhin such a drawer?

,----
| - Item 1
|   - Item 1a
|     :TASK:
| *************** TODO Inline Task
| Here is text.
| *************** END
|     :END:
|   - Item 1b
| - Item 2
| - Item 3
`----

The best solution seems to be allowing list items to get a TODO-state.
But I think this is too complicated to implement?

Regards,
Karl

  parent reply	other threads:[~2010-11-28 20:08 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
     [not found]         ` <14003_1290970935_oASJ2FXi018046_87zkst5l1u.fsf@ucl.ac.uk>
2010-11-28 20:08           ` Karl Maihofer [this message]
     [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=20101128210810.11245oaxpb4k74gs@webmail.df.eu \
    --to=ignoramus@gmx.de \
    --cc=carsten.dominik@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=n.goaziou@gmail.com \
    --cc=ucecesf@ucl.ac.uk \
    /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).