From: Richard Stallman <rms@gnu.org>
Cc: miles@gnu.org
Subject: Re: [Feature request] face property `raise'
Date: Thu, 15 May 2003 11:42:36 -0400 [thread overview]
Message-ID: <E19GKsO-0004eV-00@fencepost.gnu.org> (raw)
In-Reply-To: <67B8CED503F3D511BB9F0008C75DAD6605485601@dewdfx17> (christoph.wedler@sap.com)
In other words, the number
of direct text/overlay props, display specs, face attributes, etc which
Emacs would have to check now are not less than the number of direct
properties to check with my approach.
That is true, but it isn't really the point. Emacs can efficiently
check many face attributes because it does not have to go looking for
them in a list of other things. By contrast, Gerd found that the
number of different text properties that the redisplay code needs to
look for was crucial to the efficiency of redisplay.
Perhaps someone could find a more efficient way of handling numbers
of text properties. I don't know.
next prev parent reply other threads:[~2003-05-15 15:42 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-14 17:45 [Feature request] face property `raise' Wedler, Christoph
2003-05-14 20:57 ` Miles Bader
2003-05-15 15:42 ` Richard Stallman [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-05-13 17:17 Wedler, Christoph
2003-05-13 21:23 ` Miles Bader
2003-05-14 21:04 ` Richard Stallman
2003-04-29 18:19 Wedler, Christoph
2003-05-13 1:47 ` Richard Stallman
2003-05-13 2:22 ` Miles Bader
2003-05-14 21:05 ` Richard Stallman
2003-05-13 14:13 ` Stefan Monnier
2003-05-14 21:04 ` Richard Stallman
2003-04-11 19:34 Wedler, Christoph
2003-04-13 11:22 ` Richard Stallman
2003-04-10 18:48 Wedler, Christoph
2003-04-10 23:14 ` Kevin Rodgers
2003-04-09 18:06 Wedler, Christoph
2003-04-09 18:50 ` Kai Großjohann
2003-04-10 6:23 ` Richard Stallman
2003-04-08 17:52 Wedler, Christoph
2003-04-08 18:54 ` Kai Großjohann
2003-04-07 17:33 Wedler, Christoph
2003-04-08 6:45 ` Richard Stallman
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=E19GKsO-0004eV-00@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=miles@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).