From: Eli Zaretskii <eliz@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: 58767@debbugs.gnu.org, purity.piped@tuta.io
Subject: bug#58767: telega makes emacs crash (under an EXWM session?)
Date: Tue, 25 Oct 2022 14:35:47 +0300 [thread overview]
Message-ID: <837d0op23w.fsf@gnu.org> (raw)
In-Reply-To: <87fsfc2pjl.fsf@yahoo.com> (bug-gnu-emacs@gnu.org)
> Cc: 58767@debbugs.gnu.org
> Date: Tue, 25 Oct 2022 17:58:06 +0800
> From: Po Lu via "Bug reports for GNU Emacs,
> the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
>
> > greetings.
> > attached to this mail it's the new log, and the following is that in a pastebin:
> > https://termbin.com/4o84
> > hope this helps. Awaiting for further instructions.
> > thanks a million.
>
> AFAIU, several bugs in this area of the bidi code were fixed in Emacs 29
> (the master branch.)
I don't think so.
But to investigate, I will need a reproducible recipe, and preferably
without telega and EXWM. Specifically, what text is being displayed
when this abort happens? It looks like the buffer has some display
property, so the information about that display property will also be
needed.
Bottom line: more details are needed, including some description of
what is being done by the user and what is displayed by Emacs at the
time of the abort.
next prev parent reply other threads:[~2022-10-25 11:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-24 17:07 bug#58767: telega makes emacs crash (under an EXWM session?) Marco via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-25 0:36 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <NFCUgqi--3-9@tuta.io>
[not found] ` <87tu3s2vtn.fsf@yahoo.com>
[not found] ` <NFD5mZ9--3-9@tuta.io>
[not found] ` <87lep42unz.fsf@yahoo.com>
[not found] ` <NFDFQyP--3-9@tuta.io>
2022-10-25 9:58 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-25 11:35 ` Eli Zaretskii [this message]
2022-10-25 12:10 ` purity.piped--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-25 12:50 ` Eli Zaretskii
2022-10-25 13:31 ` Eli Zaretskii
2022-10-25 17:36 ` purity.piped--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-25 18:03 ` Eli Zaretskii
2022-10-25 18:25 ` Stefan Kangas
2022-10-27 10:05 ` purity.piped--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-27 13:22 ` Eli Zaretskii
2022-10-27 13:33 ` purity.piped--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-27 15:49 ` Eli Zaretskii
2022-10-28 0:47 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-28 8:21 ` purity.piped--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-27 13:35 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=837d0op23w.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=58767@debbugs.gnu.org \
--cc=luangruo@yahoo.com \
--cc=purity.piped@tuta.io \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.