all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: lubos.pintes@gmail.com
Cc: 68755@debbugs.gnu.org
Subject: bug#68755: 29.2; Emacs crashes repeatedly after some steps
Date: Sun, 28 Jan 2024 10:23:52 +0200	[thread overview]
Message-ID: <86fryh6f3b.fsf@gnu.org> (raw)
In-Reply-To: <86jznu7h7i.fsf@gnu.org> (message from Eli Zaretskii on Sat, 27 Jan 2024 20:40:33 +0200)

> Date: Sat, 27 Jan 2024 20:40:33 +0200
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: 68755@debbugs.gnu.org
> 
> > I made just one mistake. I didn't notice that git-bash sets the HOME 
> > variable while cmd doesn't. So I accidentally tested with two different 
> > setups.
> 
> OK, but please also answer my other question:
> 
> > > Please show everything that is displayed on the Git-bash terminal
> > > after Emacs crashes.
> 
> Seeing what you see could give some ideas.

I may have stumbled on something similar today, and fixed it.  If you
can build your own Emacs after making a small change in the C sources,
I can tell you what to change, so you could see if the crashes go away
after the change.





  reply	other threads:[~2024-01-28  8:23 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-27  9:08 bug#68755: 29.2; Emacs crashes repeatedly after some steps Ľuboš Pinteš
2024-01-27 11:25 ` Eli Zaretskii
     [not found]   ` <b7b62209-3733-4868-8a0d-bf794ad8aac4@gmail.com>
2024-01-27 13:35     ` Eli Zaretskii
2024-01-27 14:03       ` Ľuboš Pinteš
2024-01-27 14:37         ` Eli Zaretskii
2024-01-27 15:00           ` Ľuboš Pinteš
2024-01-27 15:35             ` Eli Zaretskii
2024-01-27 15:42               ` Ľuboš Pinteš
2024-01-27 15:50                 ` Eli Zaretskii
2024-01-27 17:16                   ` Ľuboš Pinteš
2024-01-27 18:40                     ` Eli Zaretskii
2024-01-28  8:23                       ` Eli Zaretskii [this message]
2024-01-28 17:46                         ` Ľuboš Pinteš
2024-01-28 19:00                           ` Corwin Brust
2024-01-28 19:37                             ` Ľuboš Pinteš
2024-01-28 20:01                               ` Eli Zaretskii

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=86fryh6f3b.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=68755@debbugs.gnu.org \
    --cc=lubos.pintes@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.