From: Samuel Wales <firstname.lastname@example.org>
To: Carsten Dominik <email@example.com>
Subject: Re: refile ideas
Date: Mon, 3 Aug 2009 15:31:55 -0700 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
On 2009-08-02, Carsten Dominik <email@example.com> wrote:
> If you mark some headlines (for example you remember targets)
> with a tag like "r", you could make yourself a restricted
> refile command like this:
> (defun my-org-restricted-refile ()
> (let ((org-refile-targets '((org-agenda-files :tag . "r"))))
> (call-interactively 'org-refile)))
> Not what you proposed, but maybe useful.
I like it.
It gives me an idea for remember. For consistency, we can
optionally make remember use restricted refile as you
The way it would work is this. A template can optionally
specify only format, not target location. When that is the
case, c-c c-c in the remember buffer asks you where you want
to file using restricted refile.
I would definitely use this, because I want to have the time
between idea and text as short as possible. Deciding the
target location does not need to happen before the text.
This would allow reduction of remember templates to just the
ones that have different formats.
It would allow you to remember to different locations from a
given template, and different templates to a given location,
without increasing the number of templates or going to a
full refile interface.
In my case, a full refile interface is /very/ slow when it gathers
candidates. But a restricted refile is much faster and reduces human
next prev parent reply other threads:[~2009-08-03 22:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-08 4:59 refile ideas Samuel Wales
2009-08-03 4:28 ` Carsten Dominik
2009-08-03 22:31 ` Samuel Wales [this message]
2009-08-04 12:44 ` Eric S Fraga
2009-08-05 6:41 ` Carsten Dominik
2009-08-05 13:00 ` Interactively add refile targets - was: " Sebastian Rose
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).