emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <dominik@science.uva.nl>
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 08:52:07 +0200	[thread overview]
Message-ID: <d1eb27c164d93b040561fb0efcc087bd@science.uva.nl> (raw)
In-Reply-To: <m2wsu1i9mu.fsf@newartisans.com>


On Oct 5, 2007, at 22:34, John Wiegley wrote:

> Carsten Dominik <dominik@science.uva.nl> writes:
>
>>> 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.

Generally overriding Lisp values would be a great feature, but I feel 
that this
implementation seems to promise that you can set any lisp value there.  
This would
lead to a large overhead, because every command would have to locally 
parse
before execution.  Also there would be uncertainties because many 
commands
act on several items etc.
I am not yet convinced that this is useful enough - so for the
time being I will stick with the LOGGING property.

Thanks for all comments!

- Carsten

      parent reply	other threads:[~2007-10-06  7:03 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
2007-10-06  6:52             ` Carsten Dominik [this message]

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=d1eb27c164d93b040561fb0efcc087bd@science.uva.nl \
    --to=dominik@science.uva.nl \
    --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).