From: Ihor Radchenko <yantar92@posteo.net>
To: Alan Mackenzie <acm@muc.de>
Cc: emacs-devel@gnu.org
Subject: Re: Should `indirect-function' be preferred over `fboundp'?
Date: Thu, 20 Jul 2023 13:08:53 +0000 [thread overview]
Message-ID: <87zg3qpw62.fsf@localhost> (raw)
In-Reply-To: <ZLkwapYDzB9QwIli@ACM>
Alan Mackenzie <acm@muc.de> writes:
> I don't think it affects the point you are making, but why are you using
> funcall in the last line, rather than just calling the funcion as
>
> (yant/foo)
I stumbled upon this behaviour in Org mode's code that works with src
blocks:
#+begin_src language
<code>
#+end_src
Org uses heuristics to determine how to fontify such code blocks:
1. Org tries to derive the major mode name from language name
constructing a symbol as (format "%s-mode" language)
2. If the symbol is a function, Org proceeds running that function to
expedite fontification.
So, no, it would not be possible to write (language-mode) directly.
Function symbol string is calculated dynamically.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2023-07-20 13:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-20 7:08 Should `indirect-function' be preferred over `fboundp'? Ihor Radchenko
2023-07-20 7:42 ` Eli Zaretskii
2023-07-20 8:23 ` Ihor Radchenko
2023-07-20 7:47 ` Andreas Schwab
2023-07-20 8:25 ` Ihor Radchenko
2023-07-20 13:02 ` Alan Mackenzie
2023-07-20 13:08 ` Ihor Radchenko [this message]
2023-07-21 1:08 ` Michael Heerdegen
2023-07-21 6:07 ` Ihor Radchenko
2023-07-22 2:49 ` Michael Heerdegen
2023-07-22 10:51 ` Ihor Radchenko
2023-07-23 2:37 ` Michael Heerdegen
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=87zg3qpw62.fsf@localhost \
--to=yantar92@posteo.net \
--cc=acm@muc.de \
--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).