emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Piotr Zielinski" <piotr.zielinski@gmail.com>
To: Carsten Dominik <dominik@science.uva.nl>
Cc: emacs-orgmode@gnu.org
Subject: Re: Another GTD question.
Date: Wed, 4 Oct 2006 19:11:22 +0200	[thread overview]
Message-ID: <3c12eb8d0610041011g22dda93ahf42608e6482f8c77@mail.gmail.com> (raw)
In-Reply-To: <76f7cd71190bcff68e57e71d163fe49f@science.uva.nl>

Hi,

In relation to Carsten's email, I'd like to ask about possible
integration of headings and plain lists.  I remember that such
integration was difficult because of the implementation of
outline-mode, but I don't know the details.  In case this is possible,
here are a few reasons why I'd like it:

1. As opposed to headings, plain list items can consists of more than
   one line.  On the other hand, they cannot be assigned tags or
   marked TODO.  So, sometimes, one has to use one or the other.  This
   is especially problematic, if you would like a TODO item below a
   multi-line plain list item.  It would be great if the features of
   headings and plain lists could be, at least to some extent,
   combined.

2. Code duplication.  At the moment, AFAIK, you need to write separate
   code for headings and plain lists.  Also, some features exist for
   both but in different forms, for example, TODO/DONE for headings is
   essentially the same as [ ]/[X] for plain lists.  I don't mind
   having different representation for the same concept as long as
   their share the same handling code.

However, I feel that any attempt at integrating integrating headings
and plain lists would require a significant rewrite.  Carsten, could
you please comment on the main difficulties of such integration?

Thanks,
Piotr

  reply	other threads:[~2006-10-04 17:11 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-26 20:03 Another GTD question Alex Bochannek
2006-09-27 12:39 ` Charles Cave
2006-09-29 10:07   ` Christopher Kuettner
2006-09-30  5:25   ` Alex Bochannek
2006-09-30 11:28     ` Carsten Dominik
2006-10-01 14:41       ` Piotr Zielinski
2006-10-02  8:58         ` Chris Lowis
2006-10-14  4:44       ` Alex Bochannek
2006-10-01 23:54     ` Charles Cave
2006-10-14  4:53       ` Alex Bochannek
2006-09-27 14:18 ` Uwe Jochum
2006-10-04 16:11 ` Carsten Dominik
2006-10-04 17:11   ` Piotr Zielinski [this message]
2006-10-20  7:54     ` Carsten Dominik
2006-10-21 20:54       ` Christopher Kuettner
     [not found]         ` <b71b18520610211738s297f8f79u227d2ce32e10d2d9@mail.gmail.com>
2006-10-22  0:39           ` Eddward DeVilla
2006-10-23  6:10             ` Carsten Dominik
2006-10-23  7:21               ` Xiao-Yong Jin
2006-10-23  7:36                 ` Carsten Dominik
2006-10-23 20:30                   ` Xiao-Yong Jin
2006-10-23 13:24               ` Eddward DeVilla
2006-10-22 11:28         ` Pete Phillips
2006-10-05 13:01   ` Jason F. McBrayer

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=3c12eb8d0610041011g22dda93ahf42608e6482f8c77@mail.gmail.com \
    --to=piotr.zielinski@gmail.com \
    --cc=dominik@science.uva.nl \
    --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).