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...
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, transient, etc.) have been merged. A lot of great features have been added to Emacs in recent years. Kudos to the maintainers!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
This isn’t true. Windows is the only major contemporary platform to use CRLF, and nowadays all major Windows text editors, especially those likely to be used by developers, can read files with LF-only line endings without jumbling all the lines together. 20 years ago, it was a different story, but that was then and this is now.
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.
[1] https://sourceforge.net/projects/android-ports-for-gnu-emacs...
Nowadays no idea, I even lost track if Emacs finally does everything that was special about XEmacs, 30 years ago.
Is there any risk of a website including a link using the Org URI scheme to load malware into your Emacs this way?
That one is fixed, though.
And it shows. Now emacs is much nicer to use on Windows. Big thanks to the developers!
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 great and waiting for 30.x to show up in packages. Congratulations.