From mboxrd@z Thu Jan 1 00:00:00 1970 From: broek@cc.umanitoba.ca Subject: org-archive-save-context-info questions Date: Tue, 27 May 2008 01:09:14 -0500 Message-ID: <20080527010914.ovrxbn2msko88coc@webware.cc.umanitoba.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; DelSp="Yes"; format="flowed" Content-Transfer-Encoding: quoted-printable Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1K0sN6-00052E-Rx for emacs-orgmode@gnu.org; Tue, 27 May 2008 02:09:20 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1K0sN5-000521-4V for emacs-orgmode@gnu.org; Tue, 27 May 2008 02:09:20 -0400 Received: from [199.232.76.173] (port=50239 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1K0sN5-00051y-0I for emacs-orgmode@gnu.org; Tue, 27 May 2008 02:09:19 -0400 Received: from mx20.gnu.org ([199.232.41.8]:57130) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1K0sN4-0002nK-G9 for emacs-orgmode@gnu.org; Tue, 27 May 2008 02:09:18 -0400 Received: from electra.cc.umanitoba.ca ([130.179.16.23]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1K0sN3-0004wV-6N for emacs-orgmode@gnu.org; Tue, 27 May 2008 02:09:17 -0400 Received: from capella.cc.umanitoba.ca (server@capella.cc.umanitoba.ca [130.179.16.13]) by electra.cc.umanitoba.ca (8.14.2/8.14.2) with ESMTP id m4R69F3J029765 for ; Tue, 27 May 2008 01:09:15 -0500 (CDT) Received: (from server@localhost) by capella.cc.umanitoba.ca (8.13.8+Sun/8.12.2) id m4R69EeB022940 for emacs-orgmode@gnu.org; Tue, 27 May 2008 01:09:14 -0500 (CDT) Content-Disposition: inline List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org Hi all, I've recently returned to regular org-mode use after a bit of a lapse =20 and have opted to start my configuration from scratch. While setting =20 up the archiving behaviour, I've discovered a few things about the =20 variable org-archive-save-context-info that strike me as undesirable =20 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 hierarch= y. Easy enough to work out for oneself, but I assume the descriptions and =20 names have been switched. 2) The customize interface for the variable presents two check-boxes =20 both labeled `TODO state.' That seemed odd. dive into the source, and =20 it looks to me and my weak elisp as though they are generated by the =20 lines in org-archive.el that read: =09 (const :tag "TODO state" todo) =09 (const :tag "TODO state" priority) It would seem to me that the second ought be described as `TODO priority'. 3) I spent a bit being very puzzled about why C-h v =20 org-archive-save-context-info yielded the claim that there was no =20 matching variable. It also didn't show up in the customize interface. =20 Puzzled, I created a dummy headline to test what would happen on =20 archiving. After archiving once, the variable exists. Is there some =20 reason for making the variable dependent upon an invocation of =20 org-archive-subtree? I doubt it will confound me again, but there =20 wouldn't have been a problem were the variable initialized when =20 org-mode is entered rather than upon a first archiving. Thanks and best, Brian vdB