From: Robert Vojta via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 68940@debbugs.gnu.org
Subject: bug#68940: 29.2; Random crashes in face for char / font
Date: Tue, 06 Feb 2024 13:29:00 +0100 [thread overview]
Message-ID: <m25xz14v5f.fsf@me.com> (raw)
In-Reply-To: <865xz1233w.fsf@gnu.org>
> Just to clarify: if you start "emacs -Q", then evaluate
>
> M-: (setq org-ellipsis (if (char-displayable-p ?⏷) "\t⏷" nil)) RET
>
> then visit some Org file and try toggling visibility (so that
> org-ellipsis is used), does it crash?
No, this one does not crash Emacs. If I get after the launch Emacs
phase, it works as expected, never crashed. An interesting fact - Emacs
launched with "--debug-init" & this ellipsis never crashed too.
- "emacs -Q" = no crash, expected
- "(setq org-ellipsis ...)" in my init.el
- "emacs --debug-init" = no crash too, never crashed
- "emacs" - crash in 80%, once running, never crashed
> If not, something else in your customizations "helps" the bug to
> happen, perhaps some font-related settings?
I'm using PragmataPro Mono font. I've tried another fonts, e.g. Menlo,
... and it is crashing w/ them too. It seems that it is not font
related.
I know that it does not crash with "emacs -Q", crashes w/ my config, and
I also know which line is causing it. Right now I'm trying to come up w/
a minimal init.el that can reproduce this issue.
Thanks.
next prev parent reply other threads:[~2024-02-06 12:29 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-05 22:46 bug#68940: 29.2; Random crashes in face for char / font Robert Vojta via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-06 12:23 ` Eli Zaretskii
2024-02-06 12:29 ` Robert Vojta via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-02-06 14:14 ` Eli Zaretskii
2024-02-06 15:55 ` Robert Vojta via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-06 16:46 ` Eli Zaretskii
2024-02-06 21:59 ` Robert Vojta via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-07 7:41 ` Robert Vojta via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-07 13:01 ` Eli Zaretskii
2024-02-08 5:42 ` Gerd Möllmann
2024-02-08 7:14 ` Eli Zaretskii
2024-02-08 7:31 ` Gerd Möllmann
2024-02-07 12:32 ` Eli Zaretskii
2024-02-07 12:50 ` Robert Vojta via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-08 6:07 ` Gerd Möllmann
2024-02-08 9:00 ` Robert Vojta via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-08 9:56 ` Robert Vojta via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-08 10:35 ` Gerd Möllmann
2024-02-09 7:22 ` Robert Vojta via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-08 10:17 ` Gerd Möllmann
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=m25xz14v5f.fsf@me.com \
--to=bug-gnu-emacs@gnu.org \
--cc=68940@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=rvojta@me.com \
/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).