all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Alan Mackenzie <acm@muc.de>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Eli Zaretskii <eliz@gnu.org>,
	stefankangas@gmail.com, Jeff Norden <jnorden@tntech.edu>,
	emacs-devel@gnu.org
Subject: Re: [PATCH] Remove obsolete fast-lock and lazy-lock libraries
Date: Wed, 12 Aug 2020 19:12:46 +0000	[thread overview]
Message-ID: <20200812191246.GA15490@ACM> (raw)
In-Reply-To: <jwvmu32ywum.fsf-monnier+emacs@gnu.org>

Hello, Stefan.

On Mon, Aug 10, 2020 at 18:19:30 -0400, Stefan Monnier wrote:
> >> > At the moment, sensible normal values are nil and jit-lock-mode.
> >> > Also sensible would be, for example, jit-lock-debug-mode, when a
> >> > user wants to compare standard jit with her own enhanced version.
> >> > It is not inconceivable that somebody might write something entirely
> >> > new to supersede jit-lock.  Why do you want to make these things
> >> > more difficult to do?
> > So the question remains: why do you want to make these more advanced
> > forms of debugging more difficult?

> I'm sorry, but you lost me: what "more advanced forms of debugging"?

My mistake, sorry: I was under the false impression that the value of
font-lock-support-mode was a function.  Looking at the code, it might
well have been in the distant past, before jit-lock was introduced in
Emacs 21.1.

[ .... ]

>         Stefan

-- 
Alan Mackenzie (Nuremberg, Germany).



  reply	other threads:[~2020-08-12 19:12 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.45.1596816008.14576.emacs-devel@gnu.org>
2020-08-09  4:04 ` [PATCH] Remove obsolete fast-lock and lazy-lock libraries Jeff Norden
2020-08-09 13:54   ` Eli Zaretskii
2020-08-09 19:21     ` Jeff Norden
2020-08-09 19:53       ` Stefan Monnier
2020-08-10  2:30         ` Eli Zaretskii
2020-08-10  4:02           ` Stefan Monnier
2020-08-10 14:02             ` Eli Zaretskii
2020-08-10 22:25               ` Stefan Monnier
2020-08-11 15:12                 ` Eli Zaretskii
2020-08-12 18:08                   ` Stefan Kangas
2020-08-12 18:28                     ` Eli Zaretskii
2020-08-12 18:53                       ` Stefan Kangas
2020-08-12 19:12                         ` Eli Zaretskii
2020-08-12 20:25                           ` Stefan Kangas
2020-08-13 13:36                             ` Eli Zaretskii
2020-08-13 14:00                               ` Stefan Monnier
2020-08-13 15:02                                 ` Stefan Kangas
2020-08-13 14:51                               ` Stefan Kangas
2020-08-13 21:30                                 ` Jeff Norden
2020-08-14  6:11                                   ` Eli Zaretskii
2020-08-14 13:32                                     ` Stefan Monnier
2020-08-10 11:04         ` Alan Mackenzie
2020-08-10 12:07           ` Stefan Monnier
2020-08-10 17:25             ` Alan Mackenzie
2020-08-10 22:19               ` Stefan Monnier
2020-08-12 19:12                 ` Alan Mackenzie [this message]
2020-08-11  3:26           ` Richard Stallman
2020-08-11  7:00             ` Jeff Norden
2020-08-09 21:34     ` Jeff Norden
2020-08-10 13:50       ` Eli Zaretskii
2020-08-10 16:59         ` Jeff Norden
2020-08-09 16:28   ` Stefan Kangas
2020-08-09 16:40     ` Alan Mackenzie
2020-08-09 20:32       ` Stefan Kangas
2020-08-09 20:49         ` Stefan Monnier
2020-08-12 18:08           ` Stefan Kangas
     [not found] <20200515175844.18941.61355@vcs0.savannah.gnu.org>
     [not found] ` <20200515175845.997EC20999@vcs0.savannah.gnu.org>
2020-05-15 18:38   ` Deleting old `:version` from defcustoms (was: master b76cdd0: Delete libraries obsolete since 23.1 and 23.2) Stefan Monnier
2020-05-15 20:58     ` Stefan Kangas
2020-08-07 15:42       ` [PATCH] Remove obsolete fast-lock and lazy-lock libraries (was: Re: Deleting old `:version` from defcustoms) Stefan Kangas
2020-08-08  2:19         ` [PATCH] Remove obsolete fast-lock and lazy-lock libraries Stefan Monnier

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200812191246.GA15490@ACM \
    --to=acm@muc.de \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=jnorden@tntech.edu \
    --cc=monnier@iro.umontreal.ca \
    --cc=stefankangas@gmail.com \
    /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 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.