From: Titus von der Malsburg <malsburg@posteo.de>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Capturing, refiling, archiving
Date: Wed, 13 May 2015 16:35:05 -0700 [thread overview]
Message-ID: <87pp64dpau.fsf@posteo.de> (raw)
In-Reply-To: <87lhgsn4kp.fsf@nicolasgoaziou.fr>
[-- Attachment #1: Type: text/plain, Size: 2351 bytes --]
On 2015-05-13 Wed 03:40, Nicolas Goaziou wrote:
> Titus von der Malsburg <malsburg@posteo.de> writes:
>
>> Capturing, refiling, and archiving all create a new entry at a target
>> location. Yet each of these facilities has it’s own way to specify the
>> target. Capture templates have the most powerful target specification
>> and refiling and archiving are both fairly limited. For users that is
>> confusing and it prevents them from getting the most out of org-mode. Is
>> there a technical reason for why different target specifications are
>> used or is it just historical? Wouldn’t it make sense to use just one
>> target specification “language” and to use that everywhere?
>
> Would you mind elaborating? What, exactly, are you suggesting?
The specification format used for capture templates seems to be the most
expressive. I was wondering if it would make sense to use that also
for refiling targets and for archiving targets. Specifically, I’d like
to be able to say things like this:
(setq org-refile-targets
'(((file+olp my-agenda-file "Agenda" "Finished") :prepend t)
((file+olp my-agenda-file "Agenda" "Urgent") :prepend t)))
and
(setq org-archive-location
'((file+olp my-agenda-file "Agenda" "Finished") :prepend t))
The reason why I think this would be useful is that some simple things
are currently not possible. Consider the following document structure:
* Office
** To do
** Finished
* Home
** To do
** Finished
If I want to archive things under the “Agenda/Finished,” there is no way
to achieve this (correct me if I’m wrong). I could try this
(setq org-archive-location "::** Finished")
but that is ambiguous. It doesn’t indicate which of the two “Finished”
nodes should be the target.
Similar problems exist for refile targets: if I want to have the first
“Finished” in my targets but not the second, how would I achieve that?
None of the available facilities allows me to do this (without changing
the document structure).
Using the capture template way of specifying targets, both problems
would be easy to solve because that mechanism allows me to specify the
complete path in the document tree leading to the node of interest
(among other things, file+regexp, etc.)
Titus
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 472 bytes --]
next prev parent reply other threads:[~2015-05-13 23:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-12 19:45 Capturing, refiling, archiving Titus von der Malsburg
2015-05-13 10:40 ` Nicolas Goaziou
2015-05-13 23:35 ` Titus von der Malsburg [this message]
2015-05-17 8:13 ` Nicolas Goaziou
2015-05-17 17:40 ` Titus von der Malsburg
2015-05-17 18:53 ` 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=87pp64dpau.fsf@posteo.de \
--to=malsburg@posteo.de \
--cc=emacs-orgmode@gnu.org \
--cc=mail@nicolasgoaziou.fr \
/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).