From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: FR: Using properties to customize global settings on a per-entry basis Date: Sat, 6 Oct 2007 08:52:07 +0200 Message-ID: References: <93a9124009e1ee0ce55829e44bf3a878@science.uva.nl> <87fy0ri1dq.fsf@bzg.ath.cx> <9cc854bff9d3fff72a5a9f7ed87235de@science.uva.nl> Mime-Version: 1.0 (Apple Message framework v624) Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Ie3gx-0002gQ-IC for emacs-orgmode@gnu.org; Sat, 06 Oct 2007 03:03:15 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Ie3gt-0002gE-WD for emacs-orgmode@gnu.org; Sat, 06 Oct 2007 03:03:14 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Ie3gt-0002gB-Pp for emacs-orgmode@gnu.org; Sat, 06 Oct 2007 03:03:11 -0400 Received: from mx20.gnu.org ([199.232.41.8]) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1Ie3gt-0002gl-4q for emacs-orgmode@gnu.org; Sat, 06 Oct 2007 03:03:11 -0400 Received: from korteweg.uva.nl ([146.50.98.70]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Ie3gs-0007i2-0Q for emacs-orgmode@gnu.org; Sat, 06 Oct 2007 03:03:10 -0400 In-Reply-To: List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: John Wiegley Cc: emacs-orgmode@gnu.org On Oct 5, 2007, at 22:34, John Wiegley wrote: > Carsten Dominik 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