From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: James Clark Newsgroups: gmane.emacs.devel Subject: Re: Propertizing the minor-mode-alist Date: Sat, 18 Sep 2004 17:52:37 +0700 Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Message-ID: <1095504757.7357.145.camel@pineapple.bkk.thaiopensource.com> References: <1095335866.7357.83.camel@pineapple.bkk.thaiopensource.com> <1095388341.7357.93.camel@pineapple.bkk.thaiopensource.com> NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1095504798 29019 80.91.229.6 (18 Sep 2004 10:53:18 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sat, 18 Sep 2004 10:53:18 +0000 (UTC) Cc: "emacs-devel@gnu.org" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Sep 18 12:53:04 2004 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1C8cpz-0007FN-00 for ; Sat, 18 Sep 2004 12:53:03 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1C8cvl-00030U-Mg for ged-emacs-devel@m.gmane.org; Sat, 18 Sep 2004 06:59:01 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1C8cvf-00030O-3T for emacs-devel@gnu.org; Sat, 18 Sep 2004 06:58:55 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1C8cvd-00030C-9I for emacs-devel@gnu.org; Sat, 18 Sep 2004 06:58:54 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1C8cvd-000309-6M for emacs-devel@gnu.org; Sat, 18 Sep 2004 06:58:53 -0400 Original-Received: from [161.58.244.53] (helo=thaiopensource.com) by monty-python.gnu.org with esmtp (TLSv1:DES-CBC3-SHA:168) (Exim 4.34) id 1C8cpf-0003fG-G5; Sat, 18 Sep 2004 06:52:44 -0400 Original-Received: from dmz-1.bkk.thaiopensource.com ([203.130.150.188]) by thaiopensource.com (8.12.11/8.11.2) with ESMTP id i8IAqfvC017668; Sat, 18 Sep 2004 17:52:42 +0700 (ICT) Original-Received: from [192.168.0.100] (home-gw.bkk.thaiopensource.com [203.130.150.187]) by dmz-1.bkk.thaiopensource.com (Postfix) with ESMTP id C9DFEFA03; Sat, 18 Sep 2004 17:52:31 +0700 (ICT) Original-To: Richard Stallman In-Reply-To: X-Mailer: Ximian Evolution 1.4.6 (1.4.6-2.1thaiopen) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: main.gmane.org gmane.emacs.devel:27221 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:27221 On Sat, 2004-09-18 at 06:23, Richard Stallman wrote: > - the code gives the new properties priority over the existing > properties > > That is the intended behavior of the feature; I don't want to change > that. I haven't been able to think of a case where this behavior would be useful. Do you have something in mind? It seems to be that, in the context of the mode-line, the other way round would be more useful: if the user has gone to the trouble of putting local-map or help-echo properties on a string destined for the mode-line, then they won't want those properties overridden by some containing :propertize element. If you think of :propertize as being a declarative description of the desired properties rather than as a function call, then given something like `(:propertize (propertize: ,(propertize s p1) ,p2) ,p3) it's more natural and useful for p1 to have priority over p2 which should in turn have priority over p3. James