From: Hrvoje Niksic <hniksic@xemacs.org>
Subject: Re: new text property
Date: Tue, 11 Jun 2002 22:40:56 +0200 [thread overview]
Message-ID: <sxsptyx5z1j.fsf@florida.munich.redhat.com> (raw)
In-Reply-To: <1023824830.26240.84.camel@space-ghost> (Colin Walters's message of "11 Jun 2002 15:47:10 -0400")
Colin Walters <walters@gnu.org> writes:
> On Tue, 2002-06-11 at 07:40, Hrvoje Niksic wrote:
>
>> Other highlighting mechanims have speed issues as well. For example,
>> Gnus prefers not to highlight huge messages because that would take
>> too long. If I controled that with `M-x font-lock-mode' (which would
>> buy me nothing in turns of convenience; Gnus has variables to
>> fine-tune its highlighting),
>
> It would be convenient because it is the same interface that one uses to
> enable and disable fontification in many prominent Emacs modes;
But in my view, that convenience does not outweigh the need for
consistency. Respecting `M-x font-lock-mode', but not any other
font-lock variable, is quite inconsistent.
>> I would expect things like `font-lock-maximum-size' to keep
>> working.
>
> Why?
Because I `M-x font-lock-mode' worked just fine. Because `C-h f
font-lock-mode' claims it does.
> There is no slowdown when using `font-lock-face'.
I never claimed that, sorry if that was unclear. Read the whole of my
paragraph, which you broke down in two pieces. It's all about
consistency between `M-x font-lock-mode' and the rest of the
font-lock-* setup (where font-lock-maximum-size is but one element),
which would be broken.
>> Plus, font-lock-maximum-decoration is not only about speed. Some
>> people don't *like* too much decoration.
>
> Well, that's a hard problem to solve.
Exactly. That's one more reason why I think it's not a good idea to
merge font-lock and other highlighting on the surface.
Again, I don't have strong feelings about this. If many users request
this feature, I will not veto its inclusion.
next prev parent reply other threads:[~2002-06-11 20:40 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-09 7:22 new text property Colin Walters
2002-06-10 4:29 ` Stephen J. Turnbull
[not found] ` <87y9dnycw8.fsf@tleepslib.sk.tsukuba.ac.jp>
2002-06-10 5:12 ` Miles Bader
2002-06-10 5:46 ` Colin Walters
[not found] ` <buod6uzbtun.fsf@mcspd15.ucom.lsi.nec.co.jp>
2002-06-10 6:38 ` Stephen J. Turnbull
[not found] ` <87bsajy6y8.fsf@tleepslib.sk.tsukuba.ac.jp>
2002-06-10 6:53 ` Colin Walters
2002-06-10 14:30 ` Stefan Monnier
[not found] ` <200206101431.g5AEV0G28267@rum.cs.yale.edu>
2002-06-10 17:35 ` Adrian Aichner
2002-06-11 5:07 ` Eli Zaretskii
2002-06-11 8:24 ` Stephen J. Turnbull
2002-06-10 8:50 ` Hrvoje Niksic
2002-06-10 11:16 ` Kai Großjohann
2002-06-10 12:07 ` Hrvoje Niksic
2002-06-10 12:26 ` Miles Bader
2002-06-10 13:32 ` Hrvoje Niksic
2002-06-10 14:28 ` Stefan Monnier
2002-06-10 15:08 ` Kai Großjohann
2002-06-10 18:51 ` Colin Walters
[not found] ` <1023735066.26240.14.camel@space-ghost>
2002-06-11 11:40 ` Hrvoje Niksic
2002-06-11 19:47 ` Colin Walters
2002-06-11 20:40 ` Hrvoje Niksic [this message]
2002-06-12 8:18 ` Kai Großjohann
2002-06-12 9:05 ` Miles Bader
2002-06-12 1:14 ` Stephen J. Turnbull
[not found] ` <877kl5pabc.fsf@tleepslib.sk.tsukuba.ac.jp>
2002-06-12 3:11 ` Colin Walters
2002-06-12 8:16 ` Stephen J. Turnbull
2002-06-12 17:46 ` Adrian Aichner
2002-06-10 15:03 ` Kai Großjohann
[not found] ` <vaf1ybf18hp.fsf@INBOX.auto.emacs.devel.tok.lucy.cs.uni-dortmund.de>
2002-06-10 15:13 ` Hrvoje Niksic
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=sxsptyx5z1j.fsf@florida.munich.redhat.com \
--to=hniksic@xemacs.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).