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

Emacs 29 is nigh

blog.phundrak.com

Post reply on HN
Print view View original

21–30 of 267 posts

Re: Emacs 29 is nigh

#21

Post by Volundr »

jmmv wrote: post #10
ilovecaching wrote: post #7

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

Yes, but what about remote support? That’s the single most thing I miss from VSCode. I want to run my editor on the local machine so that it can benefit from graphics support and integrate properly with the local windowing system, but I want all heavy lifting (LSP and the like) done on a remote machine. Yes, I can use Emacs over SSH (which I do now), but it has limitations. Yes, I could forward X11, but it’s pretty t…

> I tried TRAMP in the past, but it didn’t seem to match VSCode’s power at all in this area.

What was missing. I used TRAMP for years and aside from opening the initial file, it was identical to working locally for me. That said I haven't needed to use it in years, and haven't used the remote support in VSCode.

Re: Emacs 29 is nigh

#22

Post by jacobsenscott »

yewenjie wrote: post #12

Its great to see both eglot and tree-sitter being merged. However, I am unhappy about the state of 'emacs configurations/distributions' right now. I have been using Doom Emacs, but the development is pretty much stalled there [0], and I don't think there is any distribution that is keeping up with these cutting-edge features (compared to the NeoVim ecosystem, let's say). Somehow it feels like I was seeing a lot more…

I don't know if doom or other sort of meta-emacs distributions are as useful as they were a few years ago. Good package management is baked in to vanilla emacs now, and most any package can be configured without writing a line of elisp with the M-x customize-group.

I recently went from a whole subdirectory of configuration files to the single default init.el and have been very happy with it. I am still using `use-package` for some packages, but I don't really find it any better than just M-x package-install and M-x customize group.

In fact I would encourage new emacs users not to use some any meta-distribution or third party package management - none of them will live as long as emacs (which will live forever).

Re: Emacs 29 is nigh

#23

Post by e3bc54b2 »

YetAnotherNick wrote: post #17
yewenjie wrote: post #12

Its great to see both eglot and tree-sitter being merged. However, I am unhappy about the state of 'emacs configurations/distributions' right now. I have been using Doom Emacs, but the development is pretty much stalled there [0], and I don't think there is any distribution that is keeping up with these cutting-edge features (compared to the NeoVim ecosystem, let's say). Somehow it feels like I was seeing a lot more…

It's definitely not stalled by any metric: https://github.com/doomemacs/doomemacs/commits/master

It is not stalled, but as it currently stands, Henrik is bottleneck. He used to work like a fiend, but obviously its not sustainable for one guy to keep carrying on for something with as large scope as an Emacs distribution.

There are plans to split doom-emacs' core and contrib modules in separate modules, but no idea what the progress is on that.

Re: Emacs 29 is nigh

#24

Post by arc-in-space »

modernerd wrote: post #18
ilovecaching wrote: post #7

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…

projectile does have a command to kill all buffers from the current project that I regularly use fwiw

Re: Emacs 29 is nigh

#25

Post by letmeinhere »

fayten wrote: post #11
modernerd wrote: post #8

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? […

My preferred distribution for emacs on macos is: https://github.com/d12frosted/homebrew-emacs-plus It's well documented and supported, I highly recommend it!

yeah, options for native compilations on/off, nice custom icons, comes with a `brew service`; very solid

Re: Emacs 29 is nigh

#26

Post by yewenjie »

YetAnotherNick wrote: post #17
yewenjie wrote: post #12

Its great to see both eglot and tree-sitter being merged. However, I am unhappy about the state of 'emacs configurations/distributions' right now. I have been using Doom Emacs, but the development is pretty much stalled there [0], and I don't think there is any distribution that is keeping up with these cutting-edge features (compared to the NeoVim ecosystem, let's say). Somehow it feels like I was seeing a lot more…

It's definitely not stalled by any metric: https://github.com/doomemacs/doomemacs/commits/master

I would argue very few of those commits are feature commits of late. Once again, I am deeply thankful to Doom Emacs, and in no way 'demanding' anything from the project.

Re: Emacs 29 is nigh

#27

Post by modernerd »

ilovecaching wrote: post #20
modernerd wrote: post #18

Earlier quoted context omitted.

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…

Were you trying to make your own config, or use something prerolled like Doom?

I started with Doom to discover what features were available/useful to me. Then I built my own config from scratch recreating/borrowing only those features.

I got pretty close apart from the above sticking points. I only moved on when I realised how much time I was spending writing Emacs Lisp to solve my remaining pain points. I miss it, though!

Re: Emacs 29 is nigh

#28

Post by jmmv »

Volundr wrote: post #21
jmmv wrote: post #10

Earlier quoted context omitted.

Yes, but what about remote support? That’s the single most thing I miss from VSCode. I want to run my editor on the local machine so that it can benefit from graphics support and integrate properly with the local windowing system, but I want all heavy lifting (LSP and the like) done on a remote machine. Yes, I can use Emacs over SSH (which I do now), but it has limitations. Yes, I could forward X11, but it’s pretty t…

> I tried TRAMP in the past, but it didn’t seem to match VSCode’s power at all in this area. What was missing. I used TRAMP for years and aside from opening the initial file, it was identical to working locally for me. That said I haven't needed to use it in years, and haven't used the remote support in VSCode.

I remember running into a lot of trouble trying to get the thing to just work. There were some issues in trying to use Windows as the client and some stuff in my zshrc also got in the way. I think I was able to me it run more or less, but I gave up at the time.

I’ve recently been getting into Emacs again and have a pretty good setup already, so I’ll have to try TRAMP again.

Re: Emacs 29 is nigh

#29

Post by wrongotron »

modernerd wrote: post #8

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? […

I always grab dmg's from here: https://emacsformacosx.com/

Re: Emacs 29 is nigh

#30

Post by jimbokun »

This sounds interesting:

> This comes with a new sqlite-mode which allows you to explore SQLite databases within Emacs and to interact with them. Check out the sqlite-mode-open-file function!

Post reply on HN