[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#70914: 29.3; Crashes often on Windows
|
From: |
Ihor Radchenko |
|
Subject: |
bug#70914: 29.3; Crashes often on Windows |
|
Date: |
Thu, 23 May 2024 10:30:11 +0000 |
Eli Zaretskii <eliz@gnu.org> writes:
>> Lisp Backtrace:
>> "file-exists-p" (0xbf6f20)
>> "or" (0xbf7130)
>> "if" (0xbf72e0)
>> 0xa9e7f40 Lisp type 3
>> "org-activate-links--overlays" (0x4badb48)
>> "org-activate-links" (0x4badac0)
>> "font-lock-fontify-keywords-region" (0x4bada20)
>
> This seems to tell that font-lock calls org-activate-links, which
> calls org-activate-links--overlays, which somehow ends up calling
> file-exists-p with the "file name" that is "//". I don't see how this
> can happen, but my guess is that this is somehow related to the Org
> file being visited and displayed, so the contents of that file might
> hold a part of the solution for this riddle. Do you have a lot of
> links in that Org file? If not, could you perhaps show them?
>
> Ihor, can you help? How can org-activate-links--overlays end up
> calling file-exists-p, and what should we look for in the Org file to
> understand why it calls file-exists-p with "//"? I'm guessing this
> might be related to the htmlize-link or help-echo properties of Org
> links?
This is not something Org does directly.
We allow custom link fontification function set via :activate-func link
parameter. One of the common ways to use this :activate-func is to
highlight files that do not exist with different face.
Since the report appears to be for Doom Emacs, the likely code
responsible for calling `file-exists-p' is
https://github.com/doomemacs/doomemacs/blob/master/modules/lang/org/config.el#L500
--
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>
- bug#70914: 29.3; Crashes often on Windows, (continued)
- bug#70914: 29.3; Crashes often on Windows, Simen Endsjø, 2024/05/22
- bug#70914: 29.3; Crashes often on Windows, Eli Zaretskii, 2024/05/22
- bug#70914: 29.3; Crashes often on Windows, Simen Endsjø, 2024/05/22
- bug#70914: 29.3; Crashes often on Windows, Eli Zaretskii, 2024/05/22
- bug#70914: 29.3; Crashes often on Windows, Simen Endsjø, 2024/05/22
- bug#70914: 29.3; Crashes often on Windows, Simen Endsjø, 2024/05/22
- bug#70914: 29.3; Crashes often on Windows, Eli Zaretskii, 2024/05/23
- bug#70914: 29.3; Crashes often on Windows, Simen Endsjø, 2024/05/23
- bug#70914: 29.3; Crashes often on Windows, Eli Zaretskii, 2024/05/23
- bug#70914: 29.3; Crashes often on Windows, Simen Endsjø, 2024/05/23
- bug#70914: 29.3; Crashes often on Windows,
Ihor Radchenko <=
- bug#70914: 29.3; Crashes often on Windows, Eli Zaretskii, 2024/05/23
- bug#70914: 29.3; Crashes often on Windows, Ihor Radchenko, 2024/05/23
- bug#70914: 29.3; Crashes often on Windows, Eli Zaretskii, 2024/05/23
- bug#70914: 29.3; Crashes often on Windows, Ihor Radchenko, 2024/05/23
- bug#70914: 29.3; Crashes often on Windows, Eli Zaretskii, 2024/05/23
- bug#70914: 29.3; Crashes often on Windows, Ihor Radchenko, 2024/05/23
- bug#70914: 29.3; Crashes often on Windows, Eli Zaretskii, 2024/05/23
- bug#70914: 29.3; Crashes often on Windows, Ihor Radchenko, 2024/05/23
- bug#70914: 29.3; Crashes often on Windows, Eli Zaretskii, 2024/05/23
- bug#70914: 29.3; Crashes often on Windows, Simen Endsjø, 2024/05/23