From: Bernt Hansen <bernt@norang.ca>
To: emacs-orgmode@gnu.org
Subject: Converting lists to todo items and back
Date: Tue, 20 May 2008 13:48:11 -0400 [thread overview]
Message-ID: <87ve187tpg.fsf@gollum.intra.norang.ca> (raw)
Hi Carsten and list!
I'm finding I outline new tasks quickly with lists like this
,----
| * New Task
| - [ ] item 1
| - [ ] item 2
| - [ ] item 3
`----
and then I want to convert it to TODO items like this:
,----
| * New Task
| ** TODO item 1
| ** TODO item 2
| ** TODO item 3
`----
Is there a function to do that? If there is any extra context after the
list it should just become part of the subheading (like this)
,----[ from this ]
| * New Task
| - [ ] item 1
| detail goes here
| - more detail
| - blah
| - [ ] item 2
| More detail here
|
| end of detail
| - [ ] item 3
`----
,----[ to this ]
| * New Task
| ** TODO item 1
| detail goes here
| - more detail
| - blah
| ** TODO item 2
| More detail here
|
| end of detail
| ** TODO item 3
`----
I don't really care about the indentation on conversion since normally
my lists have little or no detail other than the list item which I want
to turn into a TODO subheading
,----[ and back again ]
| * New Task
| - [ ] item 1
| detail goes here
| - more detail
| - blah
| - [ ] item 2
| More detail here
|
| end of detail
| - [ ] item 3
`----
Would something like that be useful?
The use case I had for this was I need to test some new functionality
I'm building and I created the list of things to test as the items were
identified. This was a simple checkbox list. Later when actually
testing I needed to add more detail (SQL output with test results) which
I wanted to archive to hide the gory details so I converted the
checkboxes to TODO subheadings and added the extra detail as testing
continued.
Regards,
Bernt
next reply other threads:[~2008-05-20 17:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-20 17:48 Bernt Hansen [this message]
2008-05-20 18:04 ` Converting lists to todo items and back Paul R
2008-05-21 12:03 ` Carsten Dominik
2008-05-21 12:54 ` Bernt Hansen
2008-05-21 13:06 ` Carsten Dominik
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=87ve187tpg.fsf@gollum.intra.norang.ca \
--to=bernt@norang.ca \
--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).