all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: purity.piped@tuta.io
Cc: luangruo@yahoo.com, 58767@debbugs.gnu.org, stefankangas@gmail.com
Subject: bug#58767: telega makes emacs crash (under an EXWM session?)
Date: Thu, 27 Oct 2022 18:49:20 +0300	[thread overview]
Message-ID: <83wn8ll11b.fsf@gnu.org> (raw)
In-Reply-To: <NFOdWxw--3-9@tuta.io> (purity.piped@tuta.io)

> Date: Thu, 27 Oct 2022 15:33:48 +0200 (CEST)
> From: purity.piped@tuta.io
> Cc: stefankangas@gmail.com, luangruo@yahoo.com, 58767@debbugs.gnu.org
> 
> Yes, this is happening on emacs 29.

OK, so we'll have to keep this bug open.

> what I did was the following:
> git clone git://git.savannah.gnu.org/emacs.git emacs-debug
> cd emacs-debug
> ./autogen.sh
> ./configure CFLAGS="-O0 -g3" && make -j5 CFLAGS="-O0 -g3"
> make install PREFIX=/usr/local.
> rm -rvf ~/.config/emacs && git clone --depth=1 https://github.com/doomemacs/doomemacs ~/.config/emacs
> && ~/.config/emacs/bin/doom install && ~/.config/emacs/bin/doom sync
> note: ~/.config/ because I've set $EMACSDIR.
> this is what I did in a nutshell. if you need to reproduce what I did even more you can have my configuration
> for doom emacs; put it in $DOOMDIR (defaults to ~/.doom.d)
> https://termbin.com/hgkv
> https://termbin.com/jr3gm

Telega requires installation of stuff that I don't have and cannot
install here, sorry.  So either someone could show a recipe to
reproduce this without telega, or someone who has telega installed
will need to debug the problem.  This kind of problems need careful
study of what exactly went wrong in the display code and why.





  reply	other threads:[~2022-10-27 15:49 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 [this message]
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=83wn8ll11b.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=58767@debbugs.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.