From: Achim Gratz <Stromeko@nexgo.de>
To: emacs-orgmode@gnu.org
Subject: Re: Possible bug in org-cycle with property drawer
Date: Thu, 26 Jan 2012 18:38:18 +0100 [thread overview]
Message-ID: <8739b2weid.fsf@Rainer.invalid> (raw)
In-Reply-To: 87ipjyg886.fsf@gnu.org
Bastien <bzg@altern.org> writes:
> Thinking again about your problem, I don't find it natural to
> have #+DRAWERS /replacing/ existing drawers specified in `org-drawers',
> instead of just adding new ones.
Well, if one had defined a lot of drawers in their configuration and
wanted the list to be trimmed in a few documents...
Personally I never customize org-drawer, based on the principle that
local configuration shouldn't render documents invalid in a different
environment. Based on that principle, if you do configure the drawers
for a document, you should provide the complete list and not just some
additional configuration, so the current behaviour is perfect. If you
change it, I'd now need a way to specify that I do not want to import
the local configuration.
I'd rather have an extension to #+KEYWORD to import their existing
global counterpart, where appropriate.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
SD adaptation for Waldorf rackAttack V1.04R1:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
next prev parent reply other threads:[~2012-01-26 17:39 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 [this message]
2012-01-28 23:50 ` Bastien
2012-01-29 8:05 ` Achim Gratz
2012-01-29 9:53 ` Bastien
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=8739b2weid.fsf@Rainer.invalid \
--to=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).