From: James Clark <jjc@auth-only.jclark.com>
Cc: "emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: Re: Propertizing the minor-mode-alist
Date: Sat, 18 Sep 2004 17:52:37 +0700 [thread overview]
Message-ID: <1095504757.7357.145.camel@pineapple.bkk.thaiopensource.com> (raw)
In-Reply-To: <E1C8S4v-0001Uc-Ht@fencepost.gnu.org>
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
next prev parent reply other threads:[~2004-09-18 10:52 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-16 11:57 Propertizing the minor-mode-alist James Clark
2004-09-16 14:00 ` Stefan
2004-09-17 2:32 ` James Clark
2004-09-17 3:46 ` Stefan
2004-09-17 21:52 ` Kim F. Storm
2004-09-18 19:07 ` Richard Stallman
2004-09-17 23:23 ` Richard Stallman
2004-09-18 2:50 ` James Clark
2004-09-18 22:55 ` Richard Stallman
2004-09-19 6:07 ` David Kastrup
2004-09-19 6:35 ` James Clark
2004-09-20 0:05 ` Richard Stallman
2004-09-20 2:29 ` James Clark
2004-09-20 10:56 ` Kai Grossjohann
2004-09-21 18:31 ` Richard Stallman
2004-09-22 7:30 ` James Clark
2004-09-22 13:23 ` Stefan Monnier
2004-09-22 14:02 ` James Clark
2004-09-22 16:31 ` Stefan Monnier
2004-09-23 9:29 ` Richard Stallman
2004-09-23 13:15 ` James Clark
2004-09-24 12:08 ` Richard Stallman
2004-09-18 10:52 ` James Clark [this message]
2004-09-18 21:06 ` Stefan
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1095504757.7357.145.camel@pineapple.bkk.thaiopensource.com \
--to=jjc@auth-only.jclark.com \
--cc=emacs-devel@gnu.org \
/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.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).