[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Emacs 30 Release?
From: |
Eli Zaretskii |
Subject: |
Re: Emacs 30 Release? |
Date: |
Mon, 02 Sep 2024 14:20:47 +0300 |
> Date: Sun, 1 Sep 2024 22:15:59 +0200
> From: pinmacs@cas.cat
>
> Please be explicit if this kind of reports are useful
They are, thank you very much.
> Overall experience: Compiled emacs-30 branch on 2024-08-23 with commit
> 44c2614. I am using it since then: works better in general, I perceive
> it faster and more stable. I dedicated an effort of around 3 hours of
> upgrading the additional packages, looking at the news on emacs and
> orgmode. I am very happy that I did it, and thank you.
>
> In my case, it is possible that the next time I will search for a new
> version is in the next holidays/christmas, or in summer. I feel this is
> great (even better than emacs 29) for my production workflow
>
> Compiled it with this options (as I am user of debian stable i3wm with X11):
>
> ./configure --with-native-compilation --with-native-compilation=aot
> --with-x-toolkit=lucid
>
> Failed the part of `make -j4`. But worked with `make bootstrap` (as
> suggested by the compilation error) [1]
>
> FYI, my init.el file has 6347 lines, which installs 48 packages and has
> a lot of small programs
>
> After the upgrade, one package, pass, stopped to work, but I know it was
> time to upgrade all the packages. That's what package.el suggested, and
> it went fine, except that autoremove removed again all the packages
> installed? Solved reinstalling all the packages again, but saying no to
> autoremove
>
> I encountered 2 minor issues with orgmode that I will report in the
> corresponding list; even if that issues cannot be solved, I am very
> happy on everything as is :)
>
> The last one that I encountered today is that I could not benefit from
> the new and nice use-package-vc [2] feature. That is because my compiled
> emacs comes from previous versions and usage, and it looks like I was
> using a very old use-package version instead of the built-in, so I could
> not set up this stuff until I removed the old package
Thanks, much appreciated.