unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
* Emacs 30 Release?
@ 2024-08-21 21:43 Christopher Howard
  2024-08-22  3:50 ` Eli Zaretskii
  0 siblings, 1 reply; 14+ messages in thread
From: Christopher Howard @ 2024-08-21 21:43 UTC (permalink / raw)
  To: Emacs Devel Mailing List

Hi, I'm just curious how close we might be to the 30 release. Mostly just eager anticipation, but I was also trying to make plans for my EmacsConf videos.

-- 
📛 Christopher Howard
🚀 gemini://gem.librehacker.com
🌐 http://gem.librehacker.com

בראשית ברא אלהים את השמים ואת הארץ

^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: Emacs 30 Release?
  2024-08-21 21:43 Emacs 30 Release? Christopher Howard
@ 2024-08-22  3:50 ` Eli Zaretskii
  2024-08-22 16:35   ` Christopher Howard
  0 siblings, 1 reply; 14+ messages in thread
From: Eli Zaretskii @ 2024-08-22  3:50 UTC (permalink / raw)
  To: Christopher Howard; +Cc: emacs-devel

> From: Christopher Howard <christopher@librehacker.com>
> Date: Wed, 21 Aug 2024 13:43:03 -0800
> 
> Hi, I'm just curious how close we might be to the 30 release. Mostly just eager anticipation, but I was also trying to make plans for my EmacsConf videos.

The first pretest of Emacs 30 is in the works as we speak.  How long
it takes before the actual release will depend on the results of the
pretest -- if it turns out very stable with a few minor bug reports or
none at all, the actual release will follow quickly, in a month or so.
Failing that, it might take another month or maybe two.



^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: Emacs 30 Release?
  2024-08-22  3:50 ` Eli Zaretskii
@ 2024-08-22 16:35   ` Christopher Howard
  2024-08-22 16:56     ` : " Robert Pluim
                       ` (2 more replies)
  0 siblings, 3 replies; 14+ messages in thread
From: Christopher Howard @ 2024-08-22 16:35 UTC (permalink / raw)
  To: Eli Zaretskii; +Cc: emacs-devel, emacsconf-discuss

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Christopher Howard <christopher@librehacker.com>
>> Date: Wed, 21 Aug 2024 13:43:03 -0800
>> 
>> Hi, I'm just curious how close we might be to the 30 release. Mostly just eager anticipation, but I was also trying to make plans for my EmacsConf videos.
>
> The first pretest of Emacs 30 is in the works as we speak.  How long
> it takes before the actual release will depend on the results of the
> pretest -- if it turns out very stable with a few minor bug reports or
> none at all, the actual release will follow quickly, in a month or so.
> Failing that, it might take another month or maybe two.

Thanks, do you have plans to report back with the results of the pre-test, or should I bug you again in a week or two?

For my part, I don't really want to use Emacs 30 before it is properly released, but also I needed a decent amount of time to play around with it before the EmacsConf video upload deadline (Nov 8th). I suppose other uploaders are thinking the same thing, except for those who use bleeding edge Emacs. Hence the inquiry into this. I am not trying to rush you or anything.

-- 
Christopher Howard



^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: : Emacs 30 Release?
  2024-08-22 16:35   ` Christopher Howard
@ 2024-08-22 16:56     ` Robert Pluim
  2024-08-22 17:24     ` Juergen Fenn
  2024-08-22 17:49     ` Eli Zaretskii
  2 siblings, 0 replies; 14+ messages in thread
From: Robert Pluim @ 2024-08-22 16:56 UTC (permalink / raw)
  To: Christopher Howard; +Cc: Eli Zaretskii, emacs-devel, emacsconf-discuss

>>>>> On Thu, 22 Aug 2024 08:35:39 -0800, Christopher Howard <christopher@librehacker.com> said:

    Christopher> Eli Zaretskii <eliz@gnu.org> writes:
    >>> From: Christopher Howard <christopher@librehacker.com>
    >>> Date: Wed, 21 Aug 2024 13:43:03 -0800
    >>> 
    >>> Hi, I'm just curious how close we might be to the 30
    >>> release. Mostly just eager anticipation, but I was also trying to
    >>> make plans for my EmacsConf videos.
    >> 
    >> The first pretest of Emacs 30 is in the works as we speak.  How long
    >> it takes before the actual release will depend on the results of the
    >> pretest -- if it turns out very stable with a few minor bug reports or
    >> none at all, the actual release will follow quickly, in a month or so.
    >> Failing that, it might take another month or maybe two.

    Christopher> Thanks, do you have plans to report back with the results of the pre-test, or should I bug you again in a week or two?

    Christopher> For my part, I don't really want to use Emacs 30 before it is properly
    Christopher> released, but also I needed a decent amount of time to play around
    Christopher> with it before the EmacsConf video upload deadline (Nov 8th). I
    Christopher> suppose other uploaders are thinking the same thing, except for those
    Christopher> who use bleeding edge Emacs. Hence the inquiry into this. I am not
    Christopher> trying to rush you or anything.

Iʼd encourage you to play with it now (or maybe wait for the
pre-test): emacs-30 is in bug-fix only mode, and the sooner we get
feedback on regressions or injudicious changes the better.

Robert
-- 



^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: Emacs 30 Release?
  2024-08-22 16:35   ` Christopher Howard
  2024-08-22 16:56     ` : " Robert Pluim
@ 2024-08-22 17:24     ` Juergen Fenn
  2024-08-22 17:49     ` Eli Zaretskii
  2 siblings, 0 replies; 14+ messages in thread
From: Juergen Fenn @ 2024-08-22 17:24 UTC (permalink / raw)
  To: emacs-devel, emacsconf-discuss



Am 22.08.24 um 18:35 Uhr schrieb Christopher Howard:
> For my part, I don't really want to use Emacs 30 before it is
> properly released, but also I needed a decent amount of time to play
> around with it before the EmacsConf video upload deadline (Nov 8th).
> I suppose other uploaders are thinking the same thing, except for
> those who use bleeding edge Emacs. Hence the inquiry into this. I am
> not trying to rush you or anything.


FWIW, I've been using Emacs 30.0.60 for almost two months on macOS
Sonoma, mostly with Org Mode, AUCTeX, and a bit of Markdown Mode.
Everything works fine with my setup, except for one bug I reported which
is specific to the macOS port's use of the system clipboard, but I don't
really mind with my workflow. So you may give it a try.

Don't worry, it's Emacs.

Best regards,
Jürgen.



^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: Emacs 30 Release?
  2024-08-22 16:35   ` Christopher Howard
  2024-08-22 16:56     ` : " Robert Pluim
  2024-08-22 17:24     ` Juergen Fenn
@ 2024-08-22 17:49     ` Eli Zaretskii
  2024-08-22 19:39       ` Christopher Howard
  2 siblings, 1 reply; 14+ messages in thread
From: Eli Zaretskii @ 2024-08-22 17:49 UTC (permalink / raw)
  To: Christopher Howard; +Cc: emacs-devel, emacsconf-discuss

> From: Christopher Howard <christopher@librehacker.com>
> Cc: emacs-devel@gnu.org, emacsconf-discuss@gnu.org
> Date: Thu, 22 Aug 2024 08:35:39 -0800
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> >> From: Christopher Howard <christopher@librehacker.com>
> >> Date: Wed, 21 Aug 2024 13:43:03 -0800
> >> 
> >> Hi, I'm just curious how close we might be to the 30 release. Mostly just eager anticipation, but I was also trying to make plans for my EmacsConf videos.
> >
> > The first pretest of Emacs 30 is in the works as we speak.  How long
> > it takes before the actual release will depend on the results of the
> > pretest -- if it turns out very stable with a few minor bug reports or
> > none at all, the actual release will follow quickly, in a month or so.
> > Failing that, it might take another month or maybe two.
> 
> Thanks, do you have plans to report back with the results of the pre-test, or should I bug you again in a week or two?

I wouldn't know what to report.

Why is it important for you to be informed on the progress of the
pretest?

> For my part, I don't really want to use Emacs 30 before it is properly released, but also I needed a decent amount of time to play around with it before the EmacsConf video upload deadline (Nov 8th). I suppose other uploaders are thinking the same thing, except for those who use bleeding edge Emacs. Hence the inquiry into this. I am not trying to rush you or anything.

We never really know in advance when the release is imminent, except
when we produce a release candidate.  So just watching out for RC1
should be a good idea.



^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: Emacs 30 Release?
  2024-08-22 17:49     ` Eli Zaretskii
@ 2024-08-22 19:39       ` Christopher Howard
  2024-08-23 22:41         ` Stefan Kangas
  0 siblings, 1 reply; 14+ messages in thread
From: Christopher Howard @ 2024-08-22 19:39 UTC (permalink / raw)
  To: Eli Zaretskii; +Cc: emacs-devel, emacsconf-discuss

Eli Zaretskii <eliz@gnu.org> writes:

> I wouldn't know what to report.
>
> Why is it important for you to be informed on the progress of the
> pretest?
>

You made it sound like after the pre-test, you would know whether it was "mostly stable" or not, and thus some idea of whether it might be one month or three months until a release.

>
> We never really know in advance when the release is imminent, except
> when we produce a release candidate.  So just watching out for RC1
> should be a good idea.

Okay. Sounds like I might as well just build Emacs 30 now and start playing around with it. I'm going to make a random guess and suppose that the git branch I want is the "emacs-30" branch.

-- 
Christopher Howard



^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: Emacs 30 Release?
  2024-08-22 19:39       ` Christopher Howard
@ 2024-08-23 22:41         ` Stefan Kangas
  2024-08-26 17:01           ` Christopher Howard
  0 siblings, 1 reply; 14+ messages in thread
From: Stefan Kangas @ 2024-08-23 22:41 UTC (permalink / raw)
  To: Christopher Howard, Eli Zaretskii; +Cc: emacs-devel, emacsconf-discuss

Christopher Howard <christopher@librehacker.com> writes:

> Sounds like I might as well just build Emacs 30 now and start playing
> around with it. I'm going to make a random guess and suppose that the
> git branch I want is the "emacs-30" branch.

Yes, the branch you want is emacs-30.  I'd recommend doing that,
especially if time is concern.

You can also wait for the pretest tarballs and build them.  Make sure
you're subscribed to the info-gnu-emacs mailing list if you want to see
the announcements (they are also posted here):
https://lists.gnu.org/mailman/listinfo/info-gnu-emacs



^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: Emacs 30 Release?
  2024-08-23 22:41         ` Stefan Kangas
@ 2024-08-26 17:01           ` Christopher Howard
  2024-08-26 17:49             ` Eli Zaretskii
  0 siblings, 1 reply; 14+ messages in thread
From: Christopher Howard @ 2024-08-26 17:01 UTC (permalink / raw)
  To: Stefan Kangas; +Cc: Eli Zaretskii, emacs-devel, emacsconf-discuss

Stefan Kangas <stefankangas@gmail.com> writes:
> Yes, the branch you want is emacs-30.  I'd recommend doing that,
> especially if time is concern.
>

I just built it this morning from the emacs-30 repo branch. I am using guix's emacs-next environment, and did not have any trouble building or installing it. I just have to set the EMACSLOADPATH to the correct place, and also keep a watch on what info files I'm loading, so I'm reading the newer manuals. Thanks!

I was expecting half my code to break, or something. But undramatically, my entire init.el loaded normally without any errors or warnings. A seamless experience so far...

-- 
Christopher Howard



^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: Emacs 30 Release?
  2024-08-26 17:01           ` Christopher Howard
@ 2024-08-26 17:49             ` Eli Zaretskii
  2024-08-28 15:21               ` Post-Upgrade Breakage Philip Kaludercic
  2024-09-01 20:15               ` Emacs 30 Release? pinmacs
  0 siblings, 2 replies; 14+ messages in thread
From: Eli Zaretskii @ 2024-08-26 17:49 UTC (permalink / raw)
  To: Christopher Howard; +Cc: stefankangas, emacs-devel, emacsconf-discuss

> From: Christopher Howard <christopher@librehacker.com>
> Cc: Eli Zaretskii <eliz@gnu.org>,  emacs-devel@gnu.org,
>   emacsconf-discuss@gnu.org
> Date: Mon, 26 Aug 2024 09:01:35 -0800
> 
> Stefan Kangas <stefankangas@gmail.com> writes:
> > Yes, the branch you want is emacs-30.  I'd recommend doing that,
> > especially if time is concern.
> >
> 
> I just built it this morning from the emacs-30 repo branch. I am using guix's emacs-next environment, and did not have any trouble building or installing it. I just have to set the EMACSLOADPATH to the correct place, and also keep a watch on what info files I'm loading, so I'm reading the newer manuals. Thanks!
> 
> I was expecting half my code to break, or something. But undramatically, my entire init.el loaded normally without any errors or warnings. A seamless experience so far...

This is Emacs, so no surprises here.



^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: Post-Upgrade Breakage
  2024-08-26 17:49             ` Eli Zaretskii
@ 2024-08-28 15:21               ` Philip Kaludercic
  2024-09-01 20:15               ` Emacs 30 Release? pinmacs
  1 sibling, 0 replies; 14+ messages in thread
From: Philip Kaludercic @ 2024-08-28 15:21 UTC (permalink / raw)
  To: Eli Zaretskii
  Cc: Christopher Howard, stefankangas, emacs-devel, emacsconf-discuss

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Christopher Howard <christopher@librehacker.com>
>> Cc: Eli Zaretskii <eliz@gnu.org>,  emacs-devel@gnu.org,
>>   emacsconf-discuss@gnu.org
>> Date: Mon, 26 Aug 2024 09:01:35 -0800
>> 
>> Stefan Kangas <stefankangas@gmail.com> writes:
>> > Yes, the branch you want is emacs-30.  I'd recommend doing that,
>> > especially if time is concern.
>> >
>> 
>> I just built it this morning from the emacs-30 repo branch. I am
>> using guix's emacs-next environment, and did not have any trouble
>> building or installing it. I just have to set the EMACSLOADPATH to
>> the correct place, and also keep a watch on what info files I'm
>> loading, so I'm reading the newer manuals. Thanks!
>> 
>> I was expecting half my code to break, or something. But
>> undramatically, my entire init.el loaded normally without any errors
>> or warnings. A seamless experience so far...
>
> This is Emacs, so no surprises here.

I am not sure if this is generally true.  Sure, we who understand what
every line in your init.el and work on master don't have issues, but in
oneline discussions I frequently hear of people having issues when
upgrading from one version to another, especially if the change in the
major mode is greater than one.

It is probably not easy to debug this, but some special handling to
detect if the major mode version has changed from one startup to the
next might be useful for the average user.

-- 
	Philip Kaludercic on peregrine



^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: Emacs 30 Release?
  2024-08-26 17:49             ` Eli Zaretskii
  2024-08-28 15:21               ` Post-Upgrade Breakage Philip Kaludercic
@ 2024-09-01 20:15               ` pinmacs
  2024-09-01 20:24                 ` pinmacs
  2024-09-02 11:20                 ` Eli Zaretskii
  1 sibling, 2 replies; 14+ messages in thread
From: pinmacs @ 2024-09-01 20:15 UTC (permalink / raw)
  To: emacs-devel


[-- Attachment #1.1.1: Type: text/plain, Size: 5978 bytes --]

Hi,

Please be explicit if this kind of reports are useful

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

Cheers,
pinmacs

[1]

```
Loading newcomment...
Loading replace...
Loading emacs-lisp/tabulated-list...
Pure Lisp storage overflowed
Loading buff-menu...
Loading fringe...
Loading emacs-lisp/regexp-opt...
Loading image...

Error: error ("Invalid byte opcode: op=0, ptr=0")
   imagemagick-register-types()
byte-code("\300\301\302\303\304DD\305\306\307\310\311\312\313\314\315&\13\210\300\316\302\303\317DD\320\306\321\310\311\312\322\314\323&\13\210\324 
\207" [custom-declare-variable imagemagick-types-inhibit funcall 
function #[0 "\300\207" [(C HTML HTM INFO M TXT PDF)] 1 ""] "List of 
ImageMagick types that should never be treated as images.\nThis should 
be a list of symbols, each of which should be one of\nthe ImageMagick 
types listed by `imagemagick-types'.  The listed\nimage types are not 
registered by `imagemagick-register-types'.\n\nIf the value is t, 
inhibit the use of ImageMagick for images.\n\nIf you change this without 
using customize, you must call\n`imagemagick-register-types' 
afterwards.\n\nIf Emacs is compiled without ImageMagick support, this 
variable\nhas no effect." :type (choice (const :tag "Support all 
ImageMagick types" nil) (const :tag "Disable all ImageMagick types" t) 
(repeat symbol)) :initialize custom-initialize-default :set #[514 
"\300\2\2\"\210\301 \207" [set-default imagemagick-register-types] 5 
"\n\n(fn SYMBOL VALUE)"] :version "24.3" imagemagick-enabled-types #[0 
"\300\207" [(3FR ARW AVS BMP BMP2 BMP3 CAL CALS CMYK CMYKA CR2 CRW CUR 
CUT DCM DCR DCX DDS DJVU DNG DPX EXR FAX FITS GBR GIF GIF87 GRB HRZ ICB 
ICO ICON J2C JNG JP2 JPC JPEG JPG JPX K25 KDC MIFF MNG MRW MSL MSVG MTV 
NEF ORF OTB PBM PCD PCDS PCL PCT PCX PDB PEF PGM PICT PIX PJPEG PNG 
PNG24 PNG32 PNG8 PNM PPM PSD PTIF PWP RAF RAS RBG RGB RGBA RGBO RLA RLE 
SCR SCT SFW SGI SR2 SRF SUN SVG SVGZ TGA TIFF TIFF64 TILE TIM TTF UYVY 
VDA VICAR VID VIFF VST WBMP WPG X3F XBM XC XCF XPM XV XWD YCbCr YCbCrA 
YUV)] 1 ""] "List of ImageMagick types to treat as images.\nEach list 
element should be a string or symbol, representing one\nof the image 
types returned by `imagemagick-types'.  If the\nelement is a string, it 
is handled as a regexp that enables all\nmatching types.\n\nThe value of 
`imagemagick-enabled-types' may also be t, meaning\nto enable all types 
that ImageMagick supports.\n\nThe variable `imagemagick-types-inhibit' 
overrides this variable.\n\nIf you change this without using customize, 
you must call\n`imagemagick-register-types' afterwards.\n\nIf Emacs is 
compiled without ImageMagick support, this variable\nhas no effect." 
(choice (const :tag "Support all ImageMagick types" t) (const :tag 
"Disable all ImageMagick types" nil) (repeat :tag "List of types" 
(choice (symbol :tag "type") (regexp :tag "regexp")))) #[514 
"\300\2\2\"\210\301 \207" [set-default imagemagick-register-types] 5 
"\n\n(fn SYMBOL VALUE)"] "26.2" imagemagick-register-types] 12)
   load("image")
   (progn (load "fringe") (load "emacs-lisp/regexp-opt") (load "image") 
(load "international/fontset") (load "dnd") (load "tool-bar"))
   (if (fboundp 'x-create-frame) (progn (load "fringe") (load 
"emacs-lisp/regexp-opt") (load "image") (load "international/fontset") 
(load "dnd") (load "tool-bar")))
   load("loadup.el")
Invalid byte opcode: op=0, ptr=0
make[2]: *** [Makefile:684: emacs.pdmp] Error 255
make[2]: Leaving directory '/home/user/src-core/emacs/src'
make[1]: *** [Makefile:554: src] Error 2
make[1]: Leaving directory '/home/user/src-core/emacs'
make[1]: Entering directory '/home/user/src-core/emacs'
\***
\*** "make all" failed with exit status 2.
\***
\*** You could try to:
\*** - run "make bootstrap", which might fix the problem
\*** - run "make V=1", which displays the full commands invoked by make,
\***   to further investigate the problem
\***
make[1]: *** [Makefile:418: advice-on-failure] Error 2
make[1]: Leaving directory '/home/user/src-core/emacs'
make: *** [Makefile:374: all] Error 2
[2024-08-30 Fri 11:31:30] $ make bootstrap
```

[2] https://tony-zorman.com/posts/use-package-vc.html

[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3323 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]

^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: Emacs 30 Release?
  2024-09-01 20:15               ` Emacs 30 Release? pinmacs
@ 2024-09-01 20:24                 ` pinmacs
  2024-09-02 11:20                 ` Eli Zaretskii
  1 sibling, 0 replies; 14+ messages in thread
From: pinmacs @ 2024-09-01 20:24 UTC (permalink / raw)
  To: emacs-devel


[-- Attachment #1.1.1: Type: text/plain, Size: 465 bytes --]

... only one, tried now after the package upgrade which was not 
immediate thing to do after the upgrade and the shell evaluation with 
:async works (yeah, looks like it needed an upgraded version of the 
async package to work fine)

On 2024-09-01 22:15, pinmacs@cas.cat wrote:
> 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 🙂 


[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3323 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]

^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: Emacs 30 Release?
  2024-09-01 20:15               ` Emacs 30 Release? pinmacs
  2024-09-01 20:24                 ` pinmacs
@ 2024-09-02 11:20                 ` Eli Zaretskii
  1 sibling, 0 replies; 14+ messages in thread
From: Eli Zaretskii @ 2024-09-02 11:20 UTC (permalink / raw)
  To: pinmacs; +Cc: emacs-devel

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



^ permalink raw reply	[flat|nested] 14+ messages in thread

end of thread, other threads:[~2024-09-02 11:20 UTC | newest]

Thread overview: 14+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2024-08-21 21:43 Emacs 30 Release? Christopher Howard
2024-08-22  3:50 ` Eli Zaretskii
2024-08-22 16:35   ` Christopher Howard
2024-08-22 16:56     ` : " Robert Pluim
2024-08-22 17:24     ` Juergen Fenn
2024-08-22 17:49     ` Eli Zaretskii
2024-08-22 19:39       ` Christopher Howard
2024-08-23 22:41         ` Stefan Kangas
2024-08-26 17:01           ` Christopher Howard
2024-08-26 17:49             ` Eli Zaretskii
2024-08-28 15:21               ` Post-Upgrade Breakage Philip Kaludercic
2024-09-01 20:15               ` Emacs 30 Release? pinmacs
2024-09-01 20:24                 ` pinmacs
2024-09-02 11:20                 ` Eli Zaretskii

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).