From: Tassilo Horn <tsdh@gnu.org>
To: emacs-devel@gnu.org
Subject: Re: Path & Demo: Source View in Help Buffers
Date: Wed, 22 Sep 2021 13:32:57 +0200 [thread overview]
Message-ID: <87k0j8j0v3.fsf@gnu.org> (raw)
In-Reply-To: <DB9PR09MB4986ED02A969B52B29E8919996A29@DB9PR09MB4986.eurprd09.prod.outlook.com>
Arthur Miller <arthur.miller@live.com> writes:
>> Out of curiosity, why do you have fboundp-checks for font-lock-ensure
>> in the code? That's always true, isn't it?
>
> I don't know. Since font-lock has all its stuff abstracted into buffer
> local function variables, I am not sure if I can count it is not nil?
But it's no buffer-local variable, it's a function. If you have emacs
25.1 upwards, you have `font-lock-ensure'.
> If I can I would gladly remove the check. I appreciate advice, I am
> not so familiar with all the details of everything.
I think that's a common check for 3rd-party packages which want to keep
supporting emacs 24. But since you are hacking emacs core, there's no
need for that unless the function/variable is only defined if some
configure option is given or some lib is available. But none of the
latter applies to font-lock.el.
Bye,
Tassilo
next prev parent reply other threads:[~2021-09-22 11:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-22 8:59 Path & Demo: Source View in Help Buffers Arthur Miller
2021-09-22 10:55 ` Tassilo Horn
2021-09-22 11:06 ` Arthur Miller
2021-09-22 11:32 ` Tassilo Horn [this message]
2021-09-22 12:01 ` Arthur Miller
2021-09-22 13:42 ` Arthur Miller
2021-09-22 14:08 ` Tassilo Horn
2021-09-22 16:50 ` Arthur Miller
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=87k0j8j0v3.fsf@gnu.org \
--to=tsdh@gnu.org \
--cc=emacs-devel@gnu.org \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).