From: David Kastrup <dak@gnu.org>
Cc: Juri Linkov <juri@jurta.org>,
lennart.borgman.073@student.lu.se, teirllm@dms.auburn.edu,
emacs-devel@gnu.org
Subject: Re: Todays exercise of sanity (or does "see" really match "not"?)
Date: Tue, 22 Mar 2005 15:46:51 +0100 [thread overview]
Message-ID: <x5y8cflov8.fsf@lola.goethe.zz> (raw)
In-Reply-To: <E1DDjsT-0006YP-6U@fencepost.gnu.org> (Richard Stallman's message of "Tue, 22 Mar 2005 08:57:01 -0500")
Richard Stallman <rms@gnu.org> writes:
> The simplest solution is to treat the `display' property like
> `invisible' property and to skip the text displayed over the
> original text.
>
> I think that is the right thing to do.
It would be wrong for preview-latex, probably one of the most
important applications extensively using the display property. It is
very important that the underlying buffer text remains both searchable
and replaceable, and preview-latex uses isearch-hooks and similar to
make this as natural and convenient as possible.
It has been doing this for years, probably like all applications using
the display property on non-trivial texts.
Doing an incompatible interface change breaking such packages at the
current point of time would be misguided. Even if it weren't, it is
wrong to do such a large change in the course of the 22.1 release.
You can't expect all package authors to have adapted to such an
incompatible change as fast as that.
Please don't. I can't see any advantage of breaking working packages
right now for no currently apparent significant practical advantage.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
next prev parent reply other threads:[~2005-03-22 14:46 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-21 13:20 Todays exercise of sanity (or does "see" really match "not"?) Lennart Borgman
2005-03-21 13:49 ` Luc Teirlinck
2005-03-21 14:00 ` Lennart Borgman
2005-03-21 19:27 ` Juri Linkov
2005-03-21 20:18 ` David Kastrup
2005-03-22 13:57 ` Richard Stallman
2005-03-22 14:46 ` David Kastrup [this message]
2005-03-22 17:29 ` Juri Linkov
2005-03-22 22:22 ` David Kastrup
2005-03-23 6:21 ` Richard Stallman
2005-03-23 13:08 ` Juri Linkov
2005-03-23 14:19 ` Luc Teirlinck
2005-03-23 15:19 ` Juri Linkov
2005-03-23 17:03 ` Luc Teirlinck
2005-03-23 20:21 ` Juri Linkov
2005-03-23 20:33 ` Stefan Monnier
2005-03-23 21:16 ` Luc Teirlinck
2005-03-23 21:42 ` Luc Teirlinck
2005-03-23 22:54 ` Kim F. Storm
2005-03-24 1:18 ` Luc Teirlinck
2005-03-25 6:42 ` Richard Stallman
2005-03-23 21:44 ` Drew Adams
2005-03-24 0:21 ` Juri Linkov
2005-03-24 1:12 ` Luc Teirlinck
2005-03-25 6:41 ` Richard Stallman
2005-03-23 21:30 ` Luc Teirlinck
2005-03-24 5:18 ` Richard Stallman
2005-03-23 20:26 ` Richard Stallman
2005-03-24 0:19 ` Juri Linkov
2005-03-25 6:42 ` Richard Stallman
2005-03-23 0:59 ` Richard Stallman
2005-03-23 1:10 ` David Kastrup
2005-03-23 10:07 ` Kim F. Storm
2005-03-23 11:01 ` David Kastrup
2005-03-23 22:57 ` Kim F. Storm
2005-03-23 23:00 ` Kim F. Storm
2005-03-23 23:57 ` David Kastrup
2005-03-25 6:42 ` Richard Stallman
2005-03-23 12:59 ` Juri Linkov
2005-08-10 0:19 ` Drew Adams
2005-08-10 3:42 ` Eli Zaretskii
2005-08-10 4:19 ` Drew Adams
2005-08-10 4:03 ` Juri Linkov
2005-03-21 23:20 ` Drew Adams
2005-03-22 4:57 ` Miles Bader
2005-03-22 10:51 ` David Kastrup
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=x5y8cflov8.fsf@lola.goethe.zz \
--to=dak@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=juri@jurta.org \
--cc=lennart.borgman.073@student.lu.se \
--cc=teirllm@dms.auburn.edu \
/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).