Live data from Hacker News

Emacs 29 is nigh

blog.phundrak.com

151–160 of 267 posts

Re: Emacs 29 is nigh

#151
post #125

Earlier quoted context omitted.

I'm also on an AMD 3700X, 32G of RAM, with Emacs native compilation branch. I'm totally unaware of elisp vs native JSON parsing though, I was just using stock Eglot that came bundled with Emacs.

It's more a question of where you got your Emacs. Native compilation, native JSON parsing, and a bunch of other things are configure-time options.

Oh I see, I build from source but I’ve been using the same configure options forever (just native comp and rename the ctags binary). I’ll look them over again.

Re: Emacs 29 is nigh

#152

I am loving all this emacs love lately (I am an emacsophile), but I do find all this attention it is getting suddenly a bit surprising. Is it just that "long lines, LSP, fast syntax hightlighting" is making new people interested, or is it just us neckbeards coming out of the woods? I mean, many of these things are just a package-install away right now. I seldom see vim put in the same lime-light, for instance. Or may…

This is probably borderline flamebait, but my impression as an outsider looking in is that Richard Stallman not being as involved as he once was in setting policy for FSF projects held it back quite a bit.

Most notably, he had a long-time prohibition of any sort of FFI for both GCC and Emacs.

Yes, the reversal of that policy was more than 12 years ago at this point[1], but note how the first Emacs release with an FFI came out in late 2016[2]. Arguably it's only in the last couple of years that we've seen the floodgates open on the potential of that. E.g. TreeSitter & the SQLite interface in this upcoming Emacs 29 release is only there because of FFI.

I really respect what Stallman's done for the free software movement at large, but I think in this and a few other cases he was fighting yesterday's battles for around two decades too long.

1. https://lists.gnu.org/archive/html/emacs-devel/2010-03/msg00...

2. https://en.wikipedia.org/wiki/GNU_Emacs

Re: Emacs 29 is nigh

#153
post #32

Wow, Eglot/Treesitter/better package support in 29 make me want to try Emacs again. > Install packages from source with package.el Emacs users updating to 29: do you plan to use this instead of Straight now? If not, can you help me to understand what more Straight provides? Emacs on macOS users: do you generally compile new versions of Emacs from source, or wait for ports like Mitsuharu Yamamoto's one[1] to update? […

Just an fyi for people using straight or interested in it, its maintainer is working on an alternative called elpaca. https://github.com/progfolio/elpaca

I've been driving elpaca for some weeks now and it is fairly usable. Very fast installs. Occasional jankiness (as is to be expected from alpha software)

Re: Emacs 29 is nigh

#154
post #127

Currently on Emacs 28, on my personal machines. I see that there is a Emacs 29 pretest version available, for Windows. Are all Linux users building Emacs 29 from source?

I'm on Windows but use WSL exclusively. It opens the frame seamlessly. I'm about to build 29 from source because my Ubuntu ppa doesn't have a prepackaged 29 build.

I personally believe it's a good thing for a developer to have an intimate relationship with the construction of their primary tooling. It feels right to me, even if it hurts adoption.

Re: Emacs 29 is nigh

#155
post #50

Watching the Emacs community, I’m always just blown away by the love and adoration it gets. It’s clear to me that there’s something magical in it, but I can’t seem to tap that magic for myself. I’ve tried - really tried, including relearning lisp - to adopt Emacs roughly four times over my career; it never stuck. I understand the basic benefits, eg keyboard-optimized workflows, deep customization/malleability, etc. B…

You say "it just isn't accessible to [you]". If I'd install vanilla Emacs today or one of those distros, I'd probably feel the same, i.e. that Emacs is not for me. However, what makes Emacs great is that I can make myself at home in Emacs and design everything the way that works best for me personally, even if that is perhaps highly idiosyncratic. So my advice would be: Install Emacs and if there is something that you don't like, don't ask what you're missing, but simply change it. One thing I hated about Emacs were the RSI-inducing keybindings. And this is how I became one of the first 5 users of evil-mode (which provides vim keybindings). Over the last 15 years my Emacs config has grown to 4k+ lines and that seems bizarre, but the result is an editor that works really well with my personal way of thinking. It almost feels like an extension of my body, which means that I use it without thinking about it. It gets out of my way cognitively and doesn't add extra friction to my work which is already complicated enough. That's worth a lot to me.

Re: Emacs 29 is nigh

#156

Unrelated, but to anyone from Google. When I search for "emacs" and your product pops up a line saying "Did you mean Vi?" it really makes me want to quit using your search product. Your search is not best in breed anymore, so cute gimmicks like this are a flat turnoff.

At least the gimmick works both ways. (Try searching for “vi”.)

[deleted]

Re: Emacs 29 is nigh

#157

Unrelated, but to anyone from Google. When I search for "emacs" and your product pops up a line saying "Did you mean Vi?" it really makes me want to quit using your search product. Your search is not best in breed anymore, so cute gimmicks like this are a flat turnoff.

At least the gimmick works both ways. (Try searching for “vi”.)

It all makes sense. Google is playing the editor factions against each other so they won't contest the Chrome-based Electron editors that prop up their monopoly.

Re: Emacs 29 is nigh

#158
post #127

Currently on Emacs 28, on my personal machines. I see that there is a Emacs 29 pretest version available, for Windows. Are all Linux users building Emacs 29 from source?

I'm building from source because I want the latest features and bug fixes. It's really not that complicated. On Ubuntu, the following builds and installs Emacs into your home directory:

    sudo apt-get install build-essential
    sudo apt-get install libgtk-3-dev libtiff5-dev libgif-dev libjpeg-dev libpng-dev libxpm-dev libncurses-dev libgccjit-11-dev libgnutls28-dev texinfo

    git clone https://git.savannah.gnu.org/git/emacs.git
    cd emacs
    ./autogen.sh
    ./configure  --with-native-compilation --with-cairo --prefix=$HOME/usr
    make -j 4
    # testing:
    ./src/emacs -Q
    make install
To update:

    git pull
    make clean
    ./autogen.sh
    ./configure  --with-native-compilation --with-cairo --prefix=/home/malsburg/usr
    make -j 4
    # testing:
    ./src/emacs -Q
    make install

Re: Emacs 29 is nigh

#159

I highly recommend modern Emacs over VSCode. If you don't want to tinker, Emacs has multiple levels of preconfigured distributions like Prelude, Nano, and Doom Emacs that give the same out of the box working experience. Modern Emacs includes all of the great features of VSCode, plus much more. You get things like: - LSP support for completion, refactoring, listing. - Tree sitter support for super fast highlighting. -…

This is compelling! But I ended up abandoning Emacs in previous attempts to switch to it. In case anyone can help solve the pain points I remember: 1. Which project management tools do you recommend? (I think I was using Projectile in the past, but from what I recall it left buffers from previous projects open when switching to other projects, which ended up being kind of annoying.) 2. Any advice about automatic whit…

3. Can't you launch your compilation (or similar) and then M-x rename-buffer?

EDIT: try `g` for "refresh"/recompile.

Maybe that's just me though, not sure this is an official method.

Re: Emacs 29 is nigh

#160

I highly recommend modern Emacs over VSCode. If you don't want to tinker, Emacs has multiple levels of preconfigured distributions like Prelude, Nano, and Doom Emacs that give the same out of the box working experience. Modern Emacs includes all of the great features of VSCode, plus much more. You get things like: - LSP support for completion, refactoring, listing. - Tree sitter support for super fast highlighting. -…

This is compelling! But I ended up abandoning Emacs in previous attempts to switch to it. In case anyone can help solve the pain points I remember: 1. Which project management tools do you recommend? (I think I was using Projectile in the past, but from what I recall it left buffers from previous projects open when switching to other projects, which ended up being kind of annoying.) 2. Any advice about automatic whit…

I use projectile and perspective. Everything is integrated into my Ivy/Counsel and I have simple self documenting shortcuts for everything using General keybindings.

Until I set this up correctly the leftover buffers bothered me. Now it's part of my workflow.

I often have code from two projects side-by-side in split windows. Projectile restricts all of my actions to the appropriate project Autocomplete, code navigation, file search, fuzzy greps, everything uses the buffer's project as context.

With just two key presses I can close all buffers for any open project.

Post reply on HN