From: Achim Gratz <Stromeko@nexgo.de>
To: emacs-orgmode@gnu.org
Subject: Re: Possible bug in org-cycle with property drawer
Date: Tue, 31 Jan 2012 19:46:47 +0100 [thread overview]
Message-ID: <87ehufemlk.fsf@Rainer.invalid> (raw)
In-Reply-To: 87bopmrg0w.fsf@gnu.org
Bastien <bzg@altern.org> writes:
> I suggest this:
>
> (defconst org-persistent-drawers '(...))
> (defcustom org-custom-drawers '(...))
"Persistent" doesn't sound right to me, but "system" is also ringing a
bit hollow. Maybe one of the native english speakers has a better idea
of what name would be a more appropriate antonym to "custom"?
> Then local value of org-drawers would be computed by combining the two
> (with duplicates deletion.)
>
> Would that be consistent to you?
I'd say we might even have three groups of drawers already: first, the
ones used for core org functionality; they shouldn't be customizable at
all. Next, drawers that are used for optional functionality in org —
these should be customized together with configuring the functionality
they're used with. Last, entirely user-defined drawers that have no
special meaning within org. It's probably too late to have a separate
name space for the "org-defined" drawers so that they won't clash with
names that a user comes up...
As an example of the second type, if a user globally configures to log
into TIMESHEET, then it would be prudent to configure TIMESHEET as a
drawer instead of LOGBOOK. Likewise for local (re-)configuration of
log-/clock-into-drawer. There may be more places where behaviour like
that would need to be implemented.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Factory and User Sound Singles for Waldorf Q+, Q and microQ:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
next prev parent reply other threads:[~2012-01-31 18:47 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
2012-01-31 18:46 ` Achim Gratz [this message]
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=87ehufemlk.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).