From: Eli Zaretskii <eliz@gnu.org>
To: zanowsley@gmail.com
Cc: 74663-done@debbugs.gnu.org
Subject: bug#74663: Emacs crashes with Segfault while doing basic code editing
Date: Sat, 28 Dec 2024 13:30:58 +0200 [thread overview]
Message-ID: <86cyhct571.fsf@gnu.org> (raw)
In-Reply-To: <86cyhutdjt.fsf@gnu.org> (message from Eli Zaretskii on Sat, 14 Dec 2024 18:49:42 +0200)
> Cc: 74663@debbugs.gnu.org
> Date: Sat, 14 Dec 2024 18:49:42 +0200
> From: Eli Zaretskii <eliz@gnu.org>
>
> > Date: Sat, 14 Dec 2024 09:04:01 -0700
> > Cc: 74663@debbugs.gnu.org
> > From: Zan Owsley <zanowsley@gmail.com>
> >
> > Yes I did! It was the first time I built Emacs instead of using a
> > package manager. I have tried 27, 28, and 29 before, but this version
> > really blew me away. I couldn't believe the performance improvement I
> > saw right away, and that's before I rebuilt it with native compilation.
> > I have no idea how you sped it up like that, but it really feels nice.
> > I've been enjoying 30 so much that it sparked another deep dive into my
> > config and writing elisp for my own features this past week. So that's
> > been fun.
>
> OK, that's good news. I guess the bug can be closed now?
No further comments, so I'm now closing this bug.
next prev parent reply other threads:[~2024-12-28 11:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-02 18:35 bug#74663: Emacs crashes with Segfault while doing basic code editing Zan Owsley
2024-12-03 13:10 ` Eli Zaretskii
[not found] ` <CAFeMKvwPyAqeossiQMjqcRoq8GzKd3kVpkXK-gMDHLQhd2FXpg@mail.gmail.com>
2024-12-14 9:44 ` Eli Zaretskii
2024-12-14 16:04 ` Zan Owsley
2024-12-14 16:37 ` Corwin Brust
2024-12-14 17:48 ` Zan Owsley
2024-12-14 20:04 ` Eli Zaretskii
2024-12-14 16:49 ` Eli Zaretskii
2024-12-28 11:30 ` Eli Zaretskii [this message]
2024-12-28 15:37 ` Zan Owsley
2024-12-29 15:17 ` Corwin Brust
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=86cyhct571.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=74663-done@debbugs.gnu.org \
--cc=zanowsley@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.