* Re: "Use font-lock-support-mode rather than calling lazy-lock-mode"
[not found] ` <456A95B3.2020200@ubin.jp>
@ 2006-11-28 17:49 ` Richard Stallman
2006-11-28 20:58 ` Stefan Monnier
0 siblings, 1 reply; 7+ messages in thread
From: Richard Stallman @ 2006-11-28 17:49 UTC (permalink / raw)
Cc: emacs-devel
It seems that about half the people who posted something about
font-lock-support-mode are aware of jit-lock mode whereas
the other half got stuck with lazy-lock mode. My guess is that people actively
tracking the latest CVS branch (and thus the pretest version)
are well aware of jit-lock mode and the people who have not
bothered with CVS version wrote about lazy-lock vs fast-lock and
have not updated the web pages for some time.
What would people think of making font-lock-support-mode a no-op, and
creating some new variable people can use if they really want to use
something else instead of jit-lock?
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: "Use font-lock-support-mode rather than calling lazy-lock-mode"
2006-11-28 17:49 ` "Use font-lock-support-mode rather than calling lazy-lock-mode" Richard Stallman
@ 2006-11-28 20:58 ` Stefan Monnier
2006-11-29 6:54 ` ishikawa
2006-11-29 16:26 ` Richard Stallman
0 siblings, 2 replies; 7+ messages in thread
From: Stefan Monnier @ 2006-11-28 20:58 UTC (permalink / raw)
Cc: ishikawa, emacs-devel
> What would people think of making font-lock-support-mode a no-op, and
> creating some new variable people can use if they really want to use
> something else instead of jit-lock?
They'd think "Damn, Richard! What got into you?".
Seriously, I think we're wasting our time here: this problem does not
impact functionality.
AFAICT the OP's problem was the use of a separate package which enabled
lazy-lock. That package is hence (minorl) broken and will be fixed soon
enough when people start reporting the problem.
Stefan
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: "Use font-lock-support-mode rather than calling lazy-lock-mode"
2006-11-28 20:58 ` Stefan Monnier
@ 2006-11-29 6:54 ` ishikawa
2006-11-29 16:26 ` Richard Stallman
1 sibling, 0 replies; 7+ messages in thread
From: ishikawa @ 2006-11-29 6:54 UTC (permalink / raw)
Cc: ishikawa, rms, emacs-devel
Hi,
Stefan Monnier wrote:
>> What would people think of making font-lock-support-mode a no-op, and
>> creating some new variable people can use if they really want to use
>> something else instead of jit-lock?
>
> They'd think "Damn, Richard! What got into you?".
> Seriously, I think we're wasting our time here: this problem does not
> impact functionality.
> AFAICT the OP's problem was the use of a separate package which enabled
> lazy-lock. That package is hence (minorl) broken and will be fixed soon
> enough when people start reporting the problem.
>
>
> Stefan
The original reporter is here again. I agree.
Once enough people start to complain, the various widely used packages (and
their methods of customization) would be fixed sooner or later.
I would rather have it sooner and thus a pointer to such changes would be
nice because having such material on-line, the package maintainers will fix such
problems in a short time.
The information doesn't have to be in the manual page. A wiki or web page
accessible for such would-be trial users, among whom are package developers,
are just fine.
TIA.
Happy Hacking,
Chiaki Ishikawa
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: "Use font-lock-support-mode rather than calling lazy-lock-mode"
2006-11-28 20:58 ` Stefan Monnier
2006-11-29 6:54 ` ishikawa
@ 2006-11-29 16:26 ` Richard Stallman
2006-11-29 18:19 ` Stefan Monnier
1 sibling, 1 reply; 7+ messages in thread
From: Richard Stallman @ 2006-11-29 16:26 UTC (permalink / raw)
Cc: chiaki.ishikawa, emacs-devel
> What would people think of making font-lock-support-mode a no-op, and
> creating some new variable people can use if they really want to use
> something else instead of jit-lock?
They'd think "Damn, Richard! What got into you?".
Seriously, I think we're wasting our time here: this problem does not
impact functionality.
I am skeptical of these statements.
Could you present reasons for them?
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: "Use font-lock-support-mode rather than calling lazy-lock-mode"
2006-11-29 16:26 ` Richard Stallman
@ 2006-11-29 18:19 ` Stefan Monnier
2006-11-30 19:48 ` Richard Stallman
2006-12-01 6:29 ` ishikawa
0 siblings, 2 replies; 7+ messages in thread
From: Stefan Monnier @ 2006-11-29 18:19 UTC (permalink / raw)
Cc: chiaki.ishikawa, emacs-devel
> They'd think "Damn, Richard! What got into you?".
> Seriously, I think we're wasting our time here: this problem does not
> impact functionality.
> I am skeptical of these statements.
> Could you present reasons for them?
IIRC the "problem" was that Emacs warned the user that lazy-lock is obsolete
and that she can fix that via font-lock-support-mode. That's no loss of
functionality: lazy-lock works just as well as ever, AFAIK.
Stefan
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: "Use font-lock-support-mode rather than calling lazy-lock-mode"
2006-11-29 18:19 ` Stefan Monnier
@ 2006-11-30 19:48 ` Richard Stallman
2006-12-01 6:29 ` ishikawa
1 sibling, 0 replies; 7+ messages in thread
From: Richard Stallman @ 2006-11-30 19:48 UTC (permalink / raw)
Cc: chiaki.ishikawa, emacs-devel
IIRC the "problem" was that Emacs warned the user that lazy-lock is obsolete
and that she can fix that via font-lock-support-mode.
If that is true, I agree with you; I thought the problem was less
transparent.
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: "Use font-lock-support-mode rather than calling lazy-lock-mode"
2006-11-29 18:19 ` Stefan Monnier
2006-11-30 19:48 ` Richard Stallman
@ 2006-12-01 6:29 ` ishikawa
1 sibling, 0 replies; 7+ messages in thread
From: ishikawa @ 2006-12-01 6:29 UTC (permalink / raw)
Cc: rms, emacs-devel
Stefan Monnier wrote:
>> They'd think "Damn, Richard! What got into you?".
>> Seriously, I think we're wasting our time here: this problem does not
>> impact functionality.
>
>> I am skeptical of these statements.
>> Could you present reasons for them?
>
> IIRC the "problem" was that Emacs warned the user that lazy-lock is obsolete
> and that she can fix that via font-lock-support-mode. That's no loss of
> functionality: lazy-lock works just as well as ever, AFAIK.
>
Hi,
The original reporter
The problem here was that I got a warning about lazy-lock being deprecated and
the code that printed the warning contained "(sit-for 2)" and
the resulting behavior was not quite friendly since I could not figure out
initially where lazy-lock was invoked until I traced the code to figure out where.
I am not sure if lazy-lock mode (supplied with 22.0.90) works without showing
this warning every now and then (electric-buffer mode certainly was not usable
due to this warning message obscuring the intermediate output/input all the time.).
Basic functionality works maybe, but it was hardly usable to a testing luser.
Just my observation.
As for NOT putting the information into the info page, I concur given that
there is a NEWS entry and/or other pointers available on-line so that
the package mainteners have ample hints to fix his/her codes.
By the time, the release to the general public occurs, the kind of problems that
I faced (in relation to somewhat obscure initialize code for VM) would disapper,
hopefully.
Chiaki Ishikawa
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2006-12-01 6:29 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <456152B2.6040307@ubin.jp>
[not found] ` <E1GmQME-0005rp-VJ@fencepost.gnu.org>
[not found] ` <45641140.5050502@ubin.jp>
[not found] ` <E1Gn4h2-00057x-9s@fencepost.gnu.org>
[not found] ` <4566A16F.2030605@ubin.jp>
[not found] ` <E1Go9KM-0006hh-VC@fencepost.gnu.org>
[not found] ` <456A95B3.2020200@ubin.jp>
2006-11-28 17:49 ` "Use font-lock-support-mode rather than calling lazy-lock-mode" Richard Stallman
2006-11-28 20:58 ` Stefan Monnier
2006-11-29 6:54 ` ishikawa
2006-11-29 16:26 ` Richard Stallman
2006-11-29 18:19 ` Stefan Monnier
2006-11-30 19:48 ` Richard Stallman
2006-12-01 6:29 ` ishikawa
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.