emacs-bug-tracker
[Top][All Lists]
Advanced

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

bug#23272: closed (25.0.92; syntax-propertize-via-font-lock considered h


From: GNU bug Tracking System
Subject: bug#23272: closed (25.0.92; syntax-propertize-via-font-lock considered harmful)
Date: Sat, 29 Feb 2020 02:20:02 +0000

Your message dated Sat, 29 Feb 2020 03:19:26 +0100
with message-id <address@hidden>
and subject line Re: bug#23272: 25.0.92; syntax-propertize-via-font-lock 
considered harmful
has caused the debbugs.gnu.org bug report #23272,
regarding 25.0.92; syntax-propertize-via-font-lock considered harmful
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden.)


-- 
23272: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=23272
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: 25.0.92; syntax-propertize-via-font-lock considered harmful Date: Tue, 12 Apr 2016 01:54:01 +0300
It makes it impossible to call syntax-propertize without enabling
font-lock-mode first, e.g. when delay-mode-hooks is used.

Example:

(with-temp-buffer
  (insert "-- -*- mode: ada -*-")
  (delay-mode-hooks
    (set-auto-mode))
  (syntax-propertize (point)))

=> (error "Font-lock trying to use keywords before setting them up")

I've hit this when working on a patch in
http://debbugs.gnu.org/cgi/bugreport.cgi?bug=23223#38.



--- End Message ---
--- Begin Message --- Subject: Re: bug#23272: 25.0.92; syntax-propertize-via-font-lock considered harmful Date: Sat, 29 Feb 2020 03:19:26 +0100 User-agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux)
Lars Ingebrigtsen <address@hidden> writes:

>> Considering font-lock-syntactic-keywords are obsolete since Emacs 24,
>> this is not very important, and people should feel free to close this
>> if a fix is not found soon.
>
> OK; I'll leave it open for now, but probably closing this in a month or
> so if nothing further happens.

That was 14 weeks ago, and there have been no further comments.

I'm therefore closing this bug now.

Best regards,
Stefan Kangas


--- End Message ---

reply via email to

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