Archiving in same file opens all subtrees and leaves them open

Archiving in same file opens all subtrees and leaves them open

[Tom]

I put an ARCHIVE tag to the beginning of an org file:

#+ARCHIVE: ::* archive


and archived subtrees are put correctly under the archive heading 
in the same file.

The problem is archiving opens all subtrees in the file and leaves them
open and it messes up my nicely folded file. I have to refold the trees
manually to the previous state.

Is it a bug? Why does archiving open unrelated subtrees at all
except for the "archive" tree? And if it does shouldn't it restore
the previous folding state when it's finished?


Org-mode version 6.34c

Re: Archiving in same file opens all subtrees and leaves them open

[Carsten Dominik]

On Apr 4, 2010, at 8:42 AM, Tom wrote:

> I put an ARCHIVE tag to the beginning of an org file:
>
> #+ARCHIVE: ::* archive
>
>
> and archived subtrees are put correctly under the archive heading
> in the same file.
>
> The problem is archiving opens all subtrees in the file and leaves  
> them
> open and it messes up my nicely folded file. I have to refold the  
> trees
> manually to the previous state.
>
> Is it a bug? Why does archiving open unrelated subtrees at all
> except for the "archive" tree?

Because normally archiving goes to a different file, where this
would not be a problem.  But you can try this patch and run with
it for a while, to see if it causes any problems.  Please report back.

diff --git a/lisp/org-archive.el b/lisp/org-archive.el
index 3889207..c0f01da 100644
--- a/lisp/org-archive.el
+++ b/lisp/org-archive.el
@@ -263,7 +263,6 @@ this heading."
  		   org-odd-levels-only
  		 tr-org-odd-levels-only)))
  	  (goto-char (point-min))
-	  (show-all)
  	  (if heading
  	      (progn
  		(if (re-search-forward



> And if it does shouldn't it restore
> the previous folding state when it's finished?

Because there is currently no way to save and restore a folding state.

- Carsten

Re: Archiving in same file opens all subtrees and leaves them open

[Tom]

Carsten Dominik <carsten.dominik <at> gmail.com> writes:
> 
> Because normally archiving goes to a different file, where this
> would not be a problem.  But you can try this patch and run with
> it for a while, to see if it causes any problems.  

Thanks, I'll try it.

A possible workaround (if it does cause problems) could be opening 
only the target local archive subtree, not every tree in the file. 
I have a separate top level archive tree in the file, so I wouldn't 
mind it very much if this particular tree is opened and left open if
all the other trees are left alone.