From: Ken Mankoff <mankoff@gmail.com>
To: Mark Edgington <edgimar@gmail.com>
Cc: Bastien <bzg@gnu.org>, emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Smart archiving of subtrees with parent headlines
Date: Tue, 2 Apr 2019 09:32:37 +0200 [thread overview]
Message-ID: <CAFdBzEqfwS8v_6-EQuvAVZ-avcH2pknjT8kYSHAeZdLnrNG9uw@mail.gmail.com> (raw)
In-Reply-To: <87o95uqhbn.fsf@geus3064linuxwsm.geus.dk>
[-- Attachment #1: Type: text/plain, Size: 994 bytes --]
I'm not an advanced lisper so I hate to say "this seems like it should be
easy" - it isn't for me. But while playing around with the default archive
behavior (C-c C-x C-a OR C-c C-x C-s?), I notice that ":ARCHIVE_OLPATH:
Testing/SomeTest Archive Project" is include in the archived item. So Org
appears to know where the item should go (if not at the top level). It
seems like it should be easy to either a) put it in the right place when
archiving, b) put it in the right place at some later point in time or c)
perform a search on the archive file that at least limits the results to a
tree or subtree. I can do the last one!
-k.
On Fri, Mar 29, 2019 at 8:18 AM Ken Mankoff <mankoff@gmail.com> wrote:
>
> On 2019-03-29 at 03:23 +0100, Mark Edgington <edgimar@gmail.com> wrote...
> > But it sounds like you're saying that it won't work with the latest
> > git versions?
>
> elpa, not git. But yes, this code is expecting and calling functions no
> longer in the core code.
>
> -k.
>
>
[-- Attachment #2: Type: text/html, Size: 1493 bytes --]
prev parent reply other threads:[~2019-04-02 7:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-09 16:42 Smart archiving of subtrees with parent headlines Mark Edgington
2018-02-10 4:27 ` numbchild
2018-02-10 14:04 ` Eric S Fraga
2018-02-12 6:54 ` Ken Mankoff
2018-02-12 21:06 ` Mark Edgington
2018-02-12 22:44 ` Mark Edgington
2018-04-26 23:34 ` Bastien
2018-05-01 0:35 ` Mark Edgington
2018-05-01 9:01 ` Bastien
2019-03-28 18:13 ` Ken Mankoff
2019-03-29 2:23 ` Mark Edgington
2019-03-29 7:18 ` Ken Mankoff
2019-04-02 7:32 ` Ken Mankoff [this message]
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=CAFdBzEqfwS8v_6-EQuvAVZ-avcH2pknjT8kYSHAeZdLnrNG9uw@mail.gmail.com \
--to=mankoff@gmail.com \
--cc=bzg@gnu.org \
--cc=edgimar@gmail.com \
--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).