Bastien <b...@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