From: fatiparty--- via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Help Gnu Emacs <help-gnu-emacs@gnu.org>
Subject: rainbow-delimiters-mode, syntax-begin-function and font-lock-beginning-of-syntax-function
Date: Tue, 25 Jan 2022 14:37:55 +0100 (CET) [thread overview]
Message-ID: <MuGSFtP--3-2@tutanota.com> (raw)
In-Reply-To: <jwva6fkaryo.fsf-monnier+emacs@gnu.org>
Jan 26, 2022, 01:04 by monnier@iro.umontreal.ca:
> fatiparty@tutanota.com [2022-01-25 09:46:35] wrote:
>
>> Jan 25, 2022, 11:18 by help-gnu-emacs@gnu.org:
>>
>>>> Have looked for `font-lock-beginning-of-syntax-function' but
>>>> could not find information of possible obsolescence.
>>>>
>>> % grep font-lock-beginning-of-syntax-function etc/NEWS*
>>> etc/NEWS.19:font-lock-beginning-of-syntax-function and font-lock-keywords-case-fold-search.
>>> etc/NEWS.25:Removed 'font-lock-beginning-of-syntax-function' and the SYNTAX-BEGIN
>>> %
>>>
>> 'syntax-begin-function' has also been declared obsolete.
>>
In `etc/NEWS.25' there is the comment
** 'syntax-begin-function' is declared obsolete.
I guess that if one stops using 'syntax-begin-function', it would help remove
a dependency which would not be required in future.
> "Also" isn't quite right here: the above grep shows the other var has
> been *removed* which is different from being declared obsolete.
>
>> Would this mean that I can remove the following pieces
>>
>
> It means those pieces of code only have an effect for packages that
> still use that obsolete variable. Whether you want to remove it or not
> is a choice I can't make for you.
>
>
> Stefan
>
Right, if the version of emacs has `syntax-begin-function', then one could use that,
as has been done. I am making a new version without calls to things that would,
be obsolete, but without breaking the colouring functionality.
There is a call to flush the cache `(syntax-ppss-flush-cache 0' with
`(boundp 'syntax-begin-function)'. Would this still be necessary?
next prev parent reply other threads:[~2022-01-25 13:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-23 7:58 rainbow-delimiters-mode and syntax-begin-function fatiparty--- via Users list for the GNU Emacs text editor
[not found] ` <Mu4wPqh--3-2@tutanota.com-Mu4wX4B----2>
2022-01-24 9:55 ` rainbow-delimiters-mode, syntax-begin-function and font-lock-beginning-of-syntax-function fatiparty--- via Users list for the GNU Emacs text editor
2022-01-24 23:18 ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-01-25 8:46 ` fatiparty--- via Users list for the GNU Emacs text editor
2022-01-25 13:04 ` Stefan Monnier
2022-01-25 13:37 ` fatiparty--- via Users list for the GNU Emacs text editor [this message]
2022-01-25 13:55 ` Stefan Monnier
2022-01-25 15:05 ` fatiparty--- via Users list for the GNU Emacs text editor
2022-01-25 15:12 ` fatiparty--- via Users list for the GNU Emacs text editor
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=MuGSFtP--3-2@tutanota.com \
--to=help-gnu-emacs@gnu.org \
--cc=fatiparty@tutanota.com \
--cc=monnier@iro.umontreal.ca \
/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.
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).