different achiving mode

different achiving mode

[David Belohrad]

Dear All,

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).

Is there any already done function leading to desired behaviour? (or
eventually any hint how to achieve this)

My project trees have sometimes even 8 levels of hierarchy, and if they
are archived, it becomes a total mess to look after something.

thanks.

david

Re: different achiving mode

[Bastien]

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

Re: different achiving mode

[David Belohrad]

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

Re: different achiving mode

[Alexander Baier]

On 2014-01-04 23:39 David Belohrad wrote:
> 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.
[...]

If you do not mind having archived subtrees in your org file, you could
just use C-c C-x a, which only tags the tree at point with :ARCHIVE: and
excludes those from beeing cycled with TAB.  This way you would keep your
original structure.

HTH,
-- 
 Alexander Baier