From: Maxim Nikulin <manikulin@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Bug: org-src-font-lock-fontify-block should be wrapped with save-match-data [9.3.7 (9.3.7-4-gba6ca7-elpaplus @ mixed installation! /mnt/c/Users/toz/Weiterbildung/Soft/Emacs/ and /mnt/c/Users/toz/.emacs.d/elpa/org-plus-contrib-20200615/)
Date: Wed, 25 Aug 2021 18:56:09 +0700 [thread overview]
Message-ID: <sg5b4q$av1$1@ciao.gmane.io> (raw)
In-Reply-To: <sg38ei$t66$1@ciao.gmane.io>
In my previous message I forgot to mention the subject of the initial
bug report:
Bug: org-src-font-lock-fontify-block should be wrapped with
save-match-data [9.3.7 (9.3.7-4-gba6ca7-elpaplus @ mixed installation!
/mnt/c/Users/toz/Weiterbildung/Soft/Emacs/ and
/mnt/c/Users/toz/.emacs.d/elpa/org-plus-contrib-20200615/)
Notice "mixed installation!". Often it is source of obscure errors.
https://orgmode.org/worg/org-faq.html#mixed-install
Maybe link to FAQ item should be added to bug report template when mixed
installation is detected. Since mixed installation can be detected, I
would consider issuing a message during loading of Org mode.
On 24/08/2021 23:57, Maxim Nikulin wrote:
> On 23/08/2021 14:45, Timothy wrote:
>>
>> Thanks for your efforts. I have prepared a patch accordingly that wraps
>> org-src-font-lock-fontify-block’s body with save-match-data (attached).
>
> The following question may be dumb since I am not familiar how font lock
> works in Emacs. Is it necessary to wrap whole function? I do not see
> explicit operation with regexps. The only suspecting line is
>
> (org-font-lock-ensure)
I think, now it is irrelevant, so just for completeness: initialization
of major mode might affect match data as well
(unless (eq major-mode lang-mode) (funcall lang-mode))
next prev parent reply other threads:[~2021-08-25 11:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-20 10:07 Bug: org-src-font-lock-fontify-block should be wrapped with save-match-data [9.3.7 (9.3.7-4-gba6ca7-elpaplus @ mixed installation! /mnt/c/Users/toz/Weiterbildung/Soft/Emacs/ and /mnt/c/Users/toz/.emacs.d/elpa/org-plus-contrib-20200615/) Tobias Zawada
2021-08-23 7:45 ` Timothy
2021-08-24 16:57 ` Maxim Nikulin
2021-08-25 8:07 ` What happened to ./contrib? Martin Steffen
2021-08-25 8:44 ` Tim Cross
2021-08-25 11:47 ` Maxim Nikulin
2021-08-25 11:56 ` Maxim Nikulin [this message]
2021-08-31 11:28 ` Bug: org-src-font-lock-fontify-block should be wrapped with save-match-data [9.3.7 (9.3.7-4-gba6ca7-elpaplus @ mixed installation! /mnt/c/Users/toz/Weiterbildung/Soft/Emacs/ and /mnt/c/Users/toz/.emacs.d/elpa/org-plus-contrib-20200615/) Timothy
-- strict thread matches above, loose matches on Subject: below --
2021-08-25 4:05 Tobias Zawada
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='sg5b4q$av1$1@ciao.gmane.io' \
--to=manikulin@gmail.com \
--cc=emacs-orgmode@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/org-mode.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).