Live data from Hacker News

Emacs 31 is around the corner: The changes I'm daily driving

rahuljuliato.com

41–50 of 294 posts

Re: Emacs 31 is around the corner: The changes I'm daily driving

#41
post #33
post #28

Earlier quoted context omitted.

What are these things you have that makes Emacs a modern editor? I have cua-mode and don't show startup message. What else do I need to modernize Emacs?

treesitter (with easily installable grammars - a big pain point) / LSP integration OOTB / themability Plus now agent integration (aka GPTEL)

These are all trivial to implement?

`treesitter` grammars _are_ easy to install.

`eglot` is available OOTB, `lsp-mode` is easy to install and configure if you prefer.

`gptel` is easy to install and configure.

Re: Emacs 31 is around the corner: The changes I'm daily driving

#42
post #7

I'm happy to see these improvements. One thing that has always been annoying with Emacs is how much configuration is required to get a modern editor going. Things like Doom Emacs, and Spacemacs try to solve that problem, but both feel far removed from vanilla emacs. I wish Emacs came with several presets so with a single line, you could transform the editor to different base points. For example, most devs want treesi…

Claude: configure my Emacs such that … has worked pretty well for me lately.

Re: Emacs 31 is around the corner: The changes I'm daily driving

#43
post #29
post #7

I'm happy to see these improvements. One thing that has always been annoying with Emacs is how much configuration is required to get a modern editor going. Things like Doom Emacs, and Spacemacs try to solve that problem, but both feel far removed from vanilla emacs. I wish Emacs came with several presets so with a single line, you could transform the editor to different base points. For example, most devs want treesi…

This comment shows up on every single emacs thread and for the life of me I can't understand why. It takes one line in a shell to pull down a premade config and if that were to be built on, who would decide what gets put in? I don't think it's worth anyone's time to decide what everyone needs in a premade config.

>if that were to be built on, who would decide what gets put in?

A small number of people with taste and experience.

Like one hopes to be the case for every opinionated preset profile set.

Re: Emacs 31 is around the corner: The changes I'm daily driving

#44
post #41
post #33

Earlier quoted context omitted.

treesitter (with easily installable grammars - a big pain point) / LSP integration OOTB / themability Plus now agent integration (aka GPTEL)

These are all trivial to implement? `treesitter` grammars _are_ easy to install. `eglot` is available OOTB, `lsp-mode` is easy to install and configure if you prefer. `gptel` is easy to install and configure.

Being many things, even if "easy to install" individually, can add up to a hassle to pick, research, install, and configure them.

Re: Emacs 31 is around the corner: The changes I'm daily driving

#45

Systems like Emacs that are hyper-configurable via a text file seem tailor made for modern LLM's. If you've got a little bit of Emacs experience but bounced off of it because the learning curve was too steep I highly recommend diving back in with your agent. Agents are really good at setting up and maintaining your .emacs/init.el.

Doing this for Neovim at work and it’s so much fun. I justify the slopped config to myself because I want to get work done rather than learn the config of some random Neovim package and how it interacts with the rest of the system.

I can just ask Claude, “make leader / toggle a terminal at the bottom of the screen , and leader t swaps it to the right side” and it’ll just do that. I liked a theme but I wanted it to also change the status line of the focused window, and it just did that for me. I had an issue where the neo tree would freeze for a few seconds, and Claude figured out it was a bad interaction with the git in our toolchain, etc etc.

I have my very own text editor that I customized in plain English! I could’ve learnt spent hours learning Neovim’s style of Lua, researching packages, debugging, etc, but this gets the same stuff done way faster and lets me get to work. This was the biggest thing that kept me going back to either a preconfigured Vim setup like LazyVim or vscode. Definitely recommend.

Re: Emacs 31 is around the corner: The changes I'm daily driving

#47
back in 2nd year of university I remember thinking that vim is complicated so i went with Emacs. Now after using vim for couple years , I can't imagine going to Emacs and learning it. The availability of vim emulation in majority of text editors and IDEs has been a lifesaver

although the brief time I used Magit I was enamored I gotta say. I tried lazygit recently and it evoked the same feeling I had when trying Magit for the first time

Re: Emacs 31 is around the corner: The changes I'm daily driving

#48
post #22
post #7

I'm happy to see these improvements. One thing that has always been annoying with Emacs is how much configuration is required to get a modern editor going. Things like Doom Emacs, and Spacemacs try to solve that problem, but both feel far removed from vanilla emacs. I wish Emacs came with several presets so with a single line, you could transform the editor to different base points. For example, most devs want treesi…

Indeed. I myself am on Doom Emacs but I've increasingly been thinking of moving over to vanilla Emacs. I'm a bit worried about the transition period due to all the keybind differences but I'm sure it's not too bad.

Tell your agent what parts of Doom Emacs you actually use, and ask it to build a minimal init.el containing only those parts. You're probably only using ~2% of Doom, so the resulting init.el will likely only be a few hundred lines, and most of those lines will be comments and key bindings.

It won't be a perfect transition, but it will make it a lot smoother.

Re: Emacs 31 is around the corner: The changes I'm daily driving

#50
post #4

"Is anyone still using emacs?" Yes. I had to briefly visit the world of VSCode during a period of time when it had better AI integration than emacs did, but since I got Claude working well inside of emacs I've returned to 100% emacs. There just isn't anything like the old editors, built in the 80x24 terminal era, for getting huge swathes of code on your screen at once. I run a standard widescreen monitor with three v…

> Now I am more excited about the major releases; for instance term issues are an issue for me with the aforementioned Claude integration. Not enough to stop me, but annoying. Being a co-maintainer, I'm a bit biased, but I think you should try Ghostel ( https://github.com/dakra/ghostel ) if you aren't already. And if you are, you should report bugs so we can fix them :)

Is it conservative in what it sends, and liberal in what it accepts?
Post reply on HN