From: "Ľuboš Pinteš" <lubos.pintes@gmail.com>
To: Corwin Brust <corwin@bru.st>
Cc: 68755@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>
Subject: bug#68755: 29.2; Emacs crashes repeatedly after some steps
Date: Sun, 28 Jan 2024 20:37:26 +0100 [thread overview]
Message-ID: <87b4922e-8668-4353-878c-94efd93777ae@gmail.com> (raw)
In-Reply-To: <CAJf-WoQUCz4fhgbGXpjew-fjhUkHn+E2apHs3VgkAzwkDv6+zQ@mail.gmail.com>
Hello,
It seems fixed.
Dňa 28. 1. 2024 o 20:00 Corwin Brust napísal(a):
> Hi Ľuboš,
>
> On Sun, Jan 28, 2024 at 11:46 AM Ľuboš Pinteš <lubos.pintes@gmail.com> wrote:
>> I hate building the software in general because it almost always fails
>> and I am unable to find the bizarre errors I always receive. :)
>>
> I have created a set of Windows binaries (executable self-installer
> and unzip-and-run archive) that includes Eli's latest change.
>
> https://corwin.bru.st/emacs-29/emacs-29-c22d0a/
>
> Assuming you haven't already built Emacs from the emacs-29 branch for
> yourself, could you try downloading and running one this version and
> seeing if you can run in -nw without a crash using your config?
>
> Thanks for reporting!
next prev parent reply other threads:[~2024-01-28 19:37 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
2024-01-28 17:46 ` Ľuboš Pinteš
2024-01-28 19:00 ` Corwin Brust
2024-01-28 19:37 ` Ľuboš Pinteš [this message]
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=87b4922e-8668-4353-878c-94efd93777ae@gmail.com \
--to=lubos.pintes@gmail.com \
--cc=68755@debbugs.gnu.org \
--cc=corwin@bru.st \
--cc=eliz@gnu.org \
/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.