[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH] Remove obsolete fast-lock and lazy-lock libraries

From: Eli Zaretskii
Subject: Re: [PATCH] Remove obsolete fast-lock and lazy-lock libraries
Date: Mon, 10 Aug 2020 17:02:48 +0300

> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Date: Mon, 10 Aug 2020 00:02:01 -0400
> Cc: stefankangas@gmail.com, jnorden@tntech.edu, emacs-devel@gnu.org
> >> IMNSHO, that variable should not be a defcustom any more and we
> >> shouldn't encourage users to touch it.  IOW we should mark it obsolete.
> > Could you please elaborate on your rationale for this?
> AFAIK the only use for it is debugging.
> In non-debugging contexts, font-lock-with-jit-lock should "always" give
> better behavior than font-lock-without-jit-lock.

OK, but why does that mean we should demote it from being a defcustom?
People who need to debug font-lock are also users, and being unable to
change the value through "M-x set-variable" is an annoyance, at least
for me.

Do you see any harm in keeping it as a defcustom?

reply via email to

[Prev in Thread] Current Thread [Next in Thread]