Re: org-archive-save-context-info questions

[Carsten Dominik <C.Dominik@uva.nl>]

On May 27, 2008, at 8:09 AM, broek@cc.umanitoba.ca wrote:

>
>
>
> Hi all,
>
> I've recently returned to regular org-mode use after a bit of a  
> lapse and have opted to start my configuration from scratch. While  
> setting up the archiving behaviour, I've discovered a few things  
> about the variable org-archive-save-context-info that strike me as  
> undesirable or puzzling.
>
> 1) The docstring reads (in part):
>      itags      The local tags, in the headline of the subtree.
>      ltags      The tags the subtree inherits from further up the  
> hierarchy.
> Easy enough to work out for oneself, but I assume the descriptions  
> and names have been switched.

Fixed, thanks.

>
>
> 2) The customize interface for the variable presents two check-boxes  
> both labeled `TODO state.' That seemed odd.  dive into the source,  
> and it looks to me and my weak elisp as though they are generated by  
> the lines in org-archive.el that read:
> 	  (const :tag "TODO state" todo)
> 	  (const :tag "TODO state" priority)
> It would seem to me that the second ought be described as `TODO  
> priority'.

Fixes as well, thanks again.

>
>
> 3) I spent a bit being very puzzled about why C-h v org-archive-save- 
> context-info yielded the claim that there was no matching variable.  
> It also didn't show up in the customize interface. Puzzled, I  
> created a dummy headline to test what would happen on archiving.  
> After archiving once, the variable exists. Is there some reason for  
> making the variable dependent upon an invocation of org-archive- 
> subtree? I doubt it will confound me again, but there wouldn't have  
> been a problem were the variable initialized when org-mode is  
> entered rather than upon a first archiving.


Well, the problem here is that Org is now set up in a modular way, and  
that
many variables are in subfiles that are only loaded when needed.  I am  
aware
of the problem and would like to fix it, but I do not know a good way  
to do so.

If you like you can call `org-require-autoloaded-modules' in .emacs  
after the

    (require 'org-install)
    (org-require-autoloaded-modules)

and that will load everything.


HTH

- Carsten