From: Matthew Lundin <firstname.lastname@example.org>
Subject: Refile as top-level headlines?
Date: Wed, 14 Jan 2009 09:49:04 -0600 [thread overview]
Message-ID: <email@example.com> (raw)
I have a lot of org-files and use org-refile all the time as part of
my normal workflow. My basic approach is to remember things to an
inbox.org file and then to process the inbox GTD-style.
One thing I'm having a hard time figuring out is how to refile headers
as top level headlines in a target file. I've customized org-refile
with the following settings:
| (setq org-refile-use-outline-path 'file)
| (setq org-refile-targets '((org-agenda-files :maxlevel . 1)
| (nil :maxlevel . 3)))
(Note: the second setting in org-refile-targets gives me additional,
deeper targets in whatever file I'm visiting.)
What I'd like to see is for maxlevel to include the possibility of
filing an item as a top-level headline (at the bottom of the file).
This would make it easier to create new top-level projects directly
from my inbox. Otherwise, if the item I'm refiling doesn't naturally
fit under any of the existing top level headlines in the target file,
I have to (1) copy it by hand or (2) create a inbox heading in the
target file, which I then have to empty again as part of a separate
process (tedious with many org files).
Perhaps this desired behavior is already possible. Any advice would be
next reply other threads:[~2009-01-14 15:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-14 15:49 Matthew Lundin [this message]
2009-01-17 12:37 ` Refile as top-level headlines? Carsten Dominik
2009-01-18 16:31 ` Matthew Lundin
2009-04-04 3:04 ` Carsten Dominik
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).