unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Zan Owsley <zanowsley@gmail.com>
Cc: 74663@debbugs.gnu.org
Subject: bug#74663: Emacs crashes with Segfault while doing basic code editing
Date: Sat, 14 Dec 2024 18:49:42 +0200	[thread overview]
Message-ID: <86cyhutdjt.fsf@gnu.org> (raw)
In-Reply-To: <1c38f778-af49-43bb-a331-cd228a70b6c4@gmail.com> (message from Zan Owsley on Sat, 14 Dec 2024 09:04:01 -0700)

> 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?

Regarding the speed-up you see: Emacs 30 is indeed somewhat faster,
but I doubt that it is revolutionary faster.  I'm guessing that the
improvements you see are at least in part due to the different
configuration and build details.

> I looked you up after receiving this email as I was wondering who would 
> care to follow up with me. Saw that you're the co-maintainer and won the 
> 2023 FSF award (a belated congrats!) and figured you're just that kind 
> of guy who wants to help. Thanks for all your work - it's clear, even to 
> me, that Emacs 30 is a special release. Thanks for getting me to try it 
> and good luck with the continuing work.

Thanks, but I'm not the only one to take the credit.  This is a team
work, and we have a great team.





      parent reply	other threads:[~2024-12-14 16:49 UTC|newest]

Thread overview: 8+ 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 [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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=86cyhutdjt.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=74663@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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).