From: David Belohrad <david@belohrad.ch>
To: Bastien <bzg@gnu.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: different achiving mode
Date: Sat, 04 Jan 2014 23:39:39 +0100 [thread overview]
Message-ID: <878uuvnzh0.fsf@pcbe13433.cern.ch> (raw)
In-Reply-To: <87d2k7st0n.fsf@bzg.ath.cx>
Hi Bastien,
learning recently new things about org mode i think i have requested a
bullshit. Basically the idea was to somehow 'retain' the project tree,
or at least be able to restore its form from archive when needed. Seeing
complexity of this, it does not look like something easy to implement...
.d.
Bastien <bzg@gnu.org> writes:
> Hi David,
>
> David Belohrad <david@belohrad.ch> writes:
>
>> for a certain time I'm using ordinary archiving. I.e. moving DONE marked
>> tags to archive file. For this I'm using
>>
>> (org-advertized-archive-subtree &optional FIND-DONE)
>>
>> with shortcut C-u C-c C-x C-s, hence it will find all DONE items and
>> move them to archive.
>>
>> I have a trouble with 'how' the items are moved. If I look into archive,
>> the hiearchy is 'flattened'. What I'd like to see there is the same
>> hierarchy as I have in the original file, the same tags, but with
>> ARCHIVE tag added (eventually having entire file marked with ARCHIVE
>> tag).
>
> Mhh... I don't see how we could not flatten the hierarchy in some
> circumstances.
>
> For example:
>
> * TODO Headline
> ** DONE Task
>
> If you want to archive the DONE Task to another file, you cannot
> archive the TODO Headline with it.
>
> Or maybe I didn't understand your use-case correctly.
>
> Best,
>
> --
> Bastien
next prev parent reply other threads:[~2014-01-04 22:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-25 8:09 different achiving mode David Belohrad
2014-01-04 14:47 ` Bastien
2014-01-04 22:39 ` David Belohrad [this message]
2014-01-05 23:12 ` Alexander Baier
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=878uuvnzh0.fsf@pcbe13433.cern.ch \
--to=david@belohrad.ch \
--cc=bzg@gnu.org \
--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).