Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

What's New in Emacs 30.1?

masteringemacs.org

Post reply on HN
Print view View original

11–20 of 38 posts

Re: What's New in Emacs 30.1?

#11

Post by pbrowne011 »

Fun to see someone decide to just write a faster JSON parser because they believed it was possible. They mentioned last year that libjansson had some intermediate layer with Emacs, which led to too many memory allocations: https://lists.gnu.org/archive/html/emacs-devel/2024-03/msg00...

Also, the developer who wrote the parser (Géza Herman) was able to pass all of the tests with strange edge cases from https://seriot.ch/projects/parsing_json.html very quickly: https://lists.gnu.org/archive/html/emacs-devel/2024-03/msg00...

Re: What's New in Emacs 30.1?

#12

Post by bitwize »

jmclnx wrote: post #2

On NetBSD and OpenBSD, using emacs 29.4 I need to use gtk2 version. gtk3 will freeze X for a period of time, rarely forever when I try and use the menus. Hoping that was fixed with this version :) But my guess the issue lies with gtk3, the NetBSD people had said in some cases gtk3 acts odd. OpenBSD has the gtk2 compiled package, but on NetBSD I need to compile emacs/gtk2 myself via pkgsrc. Outside of that all works g…

The gtk maintainers ran out of fucks to give for anyone except Linux/Wayland users years ago. Honestly, emacs-lucid is the smoothest most stable experience if you're still on X11.

Re: What's New in Emacs 30.1?

#14

Post by _odey »

A note on one of the changes: "New package EditorConfig. This package provides support for the EditorConfig standard..."

Honestly the only reason to use this, and don't get me wrong, it's a huge reason, is to ensure windows users don't add CRLFs in their commits, and mess up diffs. Set `end_of_line = lf` and you're done.

`charset = utf-8` and `trim_trailing_whitespace = true` are also nice, but not as disruptive as `end_of_line`.

The other (indentation related) functionality should honestly be handled by language specific linters instead, as they can be syntax aware and allow for better control. I always disable those in practice.

This is the CLI tool to use during CI: https://github.com/editorconfig-checker/editorconfig-checker

Re: What's New in Emacs 30.1?

#16

Post by slightwinder »

> Which-key is now built in, which is good news for people who prefer that method of help (as opposed to typing C-h in a key chord).

Insane improvement. It's been years since I left Emacs, but which-key-style interfaces are the single feature I try to add everywhere. We need more of them, they are an easy UX-profit.

Re: What's New in Emacs 30.1?

#18

Post by spudlyo »

nonrandomstring wrote: post #5
idahoduncan wrote: post #4

With Emacs 30 I've stopped compiling from the master branch, preferring the tagged releases. GNU Emacs 30.0.92 (build 2, x86_64-pc-linux-gnu, GTK+ Version 3.24.33, cairo version 1.16.0) of 2024-12-03 It seems that most of the features I was eager to try from the master branch at various times (starting from native comp, then tree-sitter, use-package (although I've started using elpaca instead), modus themes, transien…

Using your thread to ask: What recommendations do people have for a build that's best for heavy org-mode use? Of all emacsen which is the best drive for Org?

I don't have any specific build-time recommendations for org-mode, but I can wholeheartedly recommend the built-in 'leuven' theme for org-mode work. I normally don't go in for light themes, but this one has so many nice little touches to spruce up org-mode elements I find myself switching to it from my usual dark doom or modus themes when working on org-mode projects.

Re: What's New in Emacs 30.1?

#19

Post by mdaniel »

_odey wrote: post #14

A note on one of the changes: "New package EditorConfig. This package provides support for the EditorConfig standard..." Honestly the only reason to use this, and don't get me wrong, it's a huge reason, is to ensure windows users don't add CRLFs in their commits, and mess up diffs. Set `end_of_line = lf` and you're done. `charset = utf-8` and `trim_trailing_whitespace = true` are also nice, but not as disruptive as `…

Merely as an observation, if you care about crlf in _commits_, then you almost certainly want https://git-scm.com/book/en/v2/Customizing-Git-Git-Configura... and not that cited EditorConfig setting. The reason is that while on a system that _uses_ crlf if you were to open those lf-only files in any text editor, it'll run the lines together into a jumble
Post reply on HN