From: broek@cc.umanitoba.ca
To: emacs-orgmode@gnu.org
Subject: org-archive-save-context-info questions
Date: Tue, 27 May 2008 01:09:14 -0500 [thread overview]
Message-ID: <20080527010914.ovrxbn2msko88coc@webware.cc.umanitoba.ca> (raw)
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.
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'.
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.
Thanks and best,
Brian vdB
next reply other threads:[~2008-05-27 6:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-27 6:09 broek [this message]
2008-05-27 6:26 ` org-archive-save-context-info questions Carsten Dominik
2008-05-27 7:20 ` broek
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=20080527010914.ovrxbn2msko88coc@webware.cc.umanitoba.ca \
--to=broek@cc.umanitoba.ca \
--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).