emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: bzg@altern.org
To: John Wiegley <johnw@newartisans.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: FR: Using properties to customize global settings on a per-entry basis
Date: Sat, 6 Oct 2007 05:06:56 +0200 (CEST)	[thread overview]
Message-ID: <57328.84.66.197.52.1191640016.squirrel@altern.org> (raw)
In-Reply-To: <m2wsu1i9mu.fsf@newartisans.com>

>>> I think using LOGGING is a bit better.
>>
>> So what do I do?  More votes?
>
> If you want to start using the facility for generally overriding Lisp
> values, then your original proposal is better.  But if this is just going
> to be for a few exceptions, LOGGING fits much better with the
> present scheme and docs.

Granted.

But to some respect Org has its own definition of 'options' (like
startup options) and I think it's clearer for users to be offered
to  use these Org options first.

A general mechanism to set org-log-done for each subtree looks
nice, but then the user will be able to mix org-log-done in its
main config, lognotedone in the startup options, and org-log-done
for some trees.  Good for advanced users, maybe slightly confusing
for others.

(I know it's bad practice to speak for "others" so I won't rely/dwell
on this too much... others can speak for themselves!)

-- 
Bastien

  reply	other threads:[~2007-10-06  2:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-29  3:50 FR: Using properties to customize global settings on a per-entry basis John Wiegley
2007-10-03 13:27 ` Carsten Dominik
2007-10-03 17:57   ` John Wiegley
2007-10-04  7:26     ` Carsten Dominik
2007-10-04 11:24       ` Bastien
2007-10-05  8:02         ` Carsten Dominik
2007-10-05 12:13           ` Bastien
2007-10-05 12:28             ` Rainer Stengele
2007-10-05 20:34           ` John Wiegley
2007-10-06  3:06             ` bzg [this message]
2007-10-06  6:52             ` Carsten Dominik

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=57328.84.66.197.52.1191640016.squirrel@altern.org \
    --to=bzg@altern.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=johnw@newartisans.com \
    /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).