From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: purity.piped@tuta.io
Cc: 58767-done@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>,
Stefan Kangas <stefankangas@gmail.com>
Subject: bug#58767: telega makes emacs crash (under an EXWM session?)
Date: Thu, 27 Oct 2022 21:35:02 +0800 [thread overview]
Message-ID: <87a65h75kp.fsf@yahoo.com> (raw)
In-Reply-To: <NFNttN6--3-9@tuta.io> (purity piped's message of "Thu, 27 Oct 2022 12:05:41 +0200 (CEST)")
purity.piped@tuta.io writes:
> greetings.
> well, I'm sorry to have to open the bug again, but it's happening again.
> usual deal, log attached and mirrored.
> to be noted: I was testing if this was an EXWM thing, but it is not, although it's strange:
> I started emacs, m-x telega, all good. C-x C-c, fired emacs once again, started telega, crash. I have recompiled emacs with the appropriate
> CFLAGS, hope this time I did it right.
> I apologize if I did not.
> thanks a million.
> best regards.
> https://termbin.com/n54s
You could send a list of the names of each group and channel you have
joined - I suspect one of them is causing the crash.
prev parent reply other threads:[~2022-10-27 13: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
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 [this message]
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=87a65h75kp.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=58767-done@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=luangruo@yahoo.com \
--cc=purity.piped@tuta.io \
--cc=stefankangas@gmail.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 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.