From: Bastien <bzg@altern.org>
To: Achim Gratz <Stromeko@nexgo.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: Possible bug in org-cycle with property drawer
Date: Sun, 29 Jan 2012 10:53:35 +0100 [thread overview]
Message-ID: <87bopmrg0w.fsf@gnu.org> (raw)
In-Reply-To: <87r4yjrl1k.fsf@Rainer.invalid> (Achim Gratz's message of "Sun, 29 Jan 2012 09:05:11 +0100")
Achim Gratz <Stromeko@nexgo.de> writes:
> Bastien <bzg@altern.org> writes:
>> This is quite a hypothetical case: the default value for `org-drawers'
>> contains drawers that are hardcoded and correspond to key features: I
>> cannot figure out a good reason for *not* having these drawers in the
>> configuration.
>
> As a customized variable org-drawers can have any content the user
> choses, including none. Before your change, the documentation said that
> drawers can be _defined_ (not added) on a per-file-basis. Past your
> change, documentation now says that drawers can be _added_ on a per-file
> basis (minor nit: org-drawers is no longer the corresponding variable to
> a file-local setting, but the basis onto which the file-local-setting is
> appended).
Yes, you're right, and you put it very well. If there is anything
that you can suggest to enhance the documentation here, please do.
`org-drawers' contains the default drawers for all files, and #+DRAWERS
lets the user add new drawers on top of these default drawers.
E.g. if a user have a "HIDE" drawer that he wants to use in any Org
buffer, it's a good idea to put it in `org-drawers'. If there is a
buffer-local drawer he want just for one file, it's a good idea to
add it using #+DRAWERS.
> Existing documents will still define _all_ drawers, not just
> the additional ones, however it seems you add them without checking if
> they are already present (I'd think add-to-list would be better than
> append).
Fixed, thanks.
> Now, there might be a good reason to have system drawers that the user
> can't change easily, but then they should not be defined in org-drawers,
> perhaps?
I suggest this:
(defconst org-persistent-drawers '(...))
(defcustom org-custom-drawers '(...))
Then local value of org-drawers would be computed by combining the two
(with duplicates deletion.)
Would that be consistent to you?
--
Bastien
next prev parent reply other threads:[~2012-01-29 9:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-25 15:48 Possible bug in org-cycle with property drawer Nick Dokos
2012-01-25 16:03 ` Carsten Dominik
2012-01-25 16:09 ` Nick Dokos
2012-01-25 16:07 ` Bastien
2012-01-25 16:17 ` Nick Dokos
2012-01-26 8:48 ` Bastien
2012-01-26 13:45 ` Nick Dokos
2012-01-26 17:38 ` Achim Gratz
2012-01-28 23:50 ` Bastien
2012-01-29 8:05 ` Achim Gratz
2012-01-29 9:53 ` Bastien [this message]
2012-01-31 18:46 ` Achim Gratz
2012-01-31 20:41 ` Nicolas Goaziou
2012-01-25 16:10 ` Bastien
2012-01-26 8:54 ` Eric S Fraga
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=87bopmrg0w.fsf@gnu.org \
--to=bzg@altern.org \
--cc=Stromeko@nexgo.de \
--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).