From mboxrd@z Thu Jan 1 00:00:00 1970 From: Titus von der Malsburg Subject: Re: Capturing, refiling, archiving Date: Wed, 13 May 2015 16:35:05 -0700 Message-ID: <87pp64dpau.fsf@posteo.de> References: <87r3qld1hb.fsf@posteo.de> <87lhgsn4kp.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:47249) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YsgBF-000474-CF for emacs-orgmode@gnu.org; Wed, 13 May 2015 19:35:14 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YsgBC-0006sK-5Y for emacs-orgmode@gnu.org; Wed, 13 May 2015 19:35:13 -0400 Received: from mx02.posteo.de ([89.146.194.165]:33491) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YsgBB-0006rQ-Vb for emacs-orgmode@gnu.org; Wed, 13 May 2015 19:35:10 -0400 In-reply-to: <87lhgsn4kp.fsf@nicolasgoaziou.fr> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Nicolas Goaziou Cc: emacs-orgmode --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 2015-05-13 Wed 03:40, Nicolas Goaziou wrote: > Titus von der Malsburg writes: > >> Capturing, refiling, and archiving all create a new entry at a target >> location. Yet each of these facilities has it=E2=80=99s own way to spec= ify 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=E2=80=99t it make sense to use ju= st one >> target specification =E2=80=9Clanguage=E2=80=9D and to use that everywhe= re? > > 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=E2=80=99d = 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 =E2=80=9CAgenda/Finished,=E2=80=9D th= ere is no way to achieve this (correct me if I=E2=80=99m wrong). I could try this (setq org-archive-location "::** Finished") but that is ambiguous. It doesn=E2=80=99t indicate which of the two =E2=80= =9CFinished=E2=80=9D nodes should be the target. Similar problems exist for refile targets: if I want to have the first =E2=80=9CFinished=E2=80=9D in my targets but not the second, how would I ac= hieve 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 =20=20=20=20 --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJVU9+pAAoJEK40WfPGE2idL2QIAJVTUe+5pIxm8aplKl92p+hU faWUMNqaRwbnjeYFpWUeFzvtVHphsmrNlUQkv3GgLTAq+7cYGeJyyhJqhQReEDjb BlQ4buZ67E3UU+CbrCwvOfP3MO/EvX7WwsyDMcATU9vwvOmm5uum9nQ3ZFQcz7pM EwE8pavK82jMP0G4H9FuyA4ieOJ0pzn58ULmF+WR4mVcZKmqT6f/TpCr8xW5lFDC C1ou0z6wnSBd/V6U9Z/rrrgc2iRhL2FOSFAJKc0BN9+6AVWgZTOKL5HTRIl7BurQ TLRDQLuADU8espoglHnhKhyJn1XCB1ThzyWzDQPvMwZg8UI94k8YyF2T88KiWjE= =NmC+ -----END PGP SIGNATURE----- --=-=-=--