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

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

rahuljuliato.com

Post reply on HN
Print view View original

141–150 of 294 posts

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

#141

Post by jerf »

joshuastuden wrote: post #60
jerf wrote: 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…

Why not use agent-shell? It makes the whole experience great. Also claude-code-ide.el. try these

I use claude-code.

I've been trying to use agent-shell with OpenCode but the abstraction that agent-shell puts on top of it is too much. I can't figure out how to change the model. The command to do it doesn't do anything; I see the correct model list and seem to be able to select it, but then it doesn't change. If I just run "opencode" in the same directory it comes up configured the way I want. The Claude integration works with that workflow too. Opencode comes up with some baby CPU-only model that I've never heard of, and basically, it outputs syntactically correct English sentences but doesn't seem to do much more than that.

Since I mostly use Claude I haven't fussed with agent-shell much yet.

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

#143

Post by wmedrano »

jlouis wrote: post #100

If you do any kind of serious work, you need a text editor. Emacs is still one of the best around. It's fast. It's configurable. And it's under your control. You won't suddenly find your text editor "upgraded" with tons of new features you never asked for. It's all opt-in.

haha, I definitely wouldn't call my setup fast. But it did get a lot better after Native Compilation and a lot of the major stuff has started async to feel more responsive at least.

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

#144

Post by jordigh »

drob518 wrote: post #113
mesrik wrote: post #75

"Is anyone still using emacs?" Yes, 34 years and no plans to switch. Emacs cursor movement keystrokes are quite widely supported elsewhere too which use GNU readline or implement at least subset themselves. Those work well also besides shells with Chromium/Chrome/Safari etc. many browsers input fields (address bar and text area). Cisco IOS, Juniper Junos, Netscreen load balancers too etc. IMHO makes jumping around CL…

Nearly 40 years for me. Wow! I’d note that MacOS input fields also have basic Emacs bindings for cursor movement, not just shells and browsers. Works in MacOS Mail, Evernote, etc.

Wow, so you used the earliest public versions. Ever written a retrospective of what 40 years of Emacs has been like?

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

#145

Post by dietr1ch »

RedCinnabar wrote: post #142

What’s the appeal of an editor like Emacs in 2026? Why’d anyone still use when most jobs nowadays require you to work inside a container (and therefore use VSCode container extension)?

Can't you ssh into them? If so, in emacs you can just open /ssh:host:path/to/file and remotely edit that file.

Even if you didn't have emacs, I don't think you are forced to use VSCode. You could just use sshfs and use any local editor, but I guess other editors also have remote editing plugins

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

#146

Post by killix »

bryanlarsen wrote: post #48
quibono wrote: post #22

Earlier quoted context omitted.

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.

[flagged]

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

#147

Post by musebox35 »

jerf wrote: 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…

I also have been using emacs for almost anything for the past 20 years. I had to switch to VSCode for coding over a remote ssh connection to cloud VMs. The client/server split of vscode felt superior over the ssh connection and the emacs alternatives was not up to the same level of performance two years ago. Do you know any progress on that front? I would love to go back to emacs as my daily driver but I am sensitive to lags when I type / execute commands. Have you worked with ai assistants over a remote connection?

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

#148

Post by mftb »

mesrik wrote: post #127
drob518 wrote: post #113

Earlier quoted context omitted.

Nearly 40 years for me. Wow! I’d note that MacOS input fields also have basic Emacs bindings for cursor movement, not just shells and browsers. Works in MacOS Mail, Evernote, etc.

Yes, emacs keystrokes became kind of cli lingua franca, which apparently many do not know. I don't remember my self ever read about those supported explicitly anywhere, but accidentally I found out long time ago and then whenever I try new systems, programs and whatever I try which keystrokes do work. Quite often at least some work.

It's GNU Readline[0] or similar. It's all over the place, on Linux at least. Being GNU it defaults to emacs, but the vi support is also excellent. The first thing I type in any foreign bash is 'set -o vi'.

[0] - https://en.wikipedia.org/wiki/GNU_Readline

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

#149

Post by sph »

aag wrote: post #106
mesrik wrote: post #75

"Is anyone still using emacs?" Yes, 34 years and no plans to switch. Emacs cursor movement keystrokes are quite widely supported elsewhere too which use GNU readline or implement at least subset themselves. Those work well also besides shells with Chromium/Chrome/Safari etc. many browsers input fields (address bar and text area). Cisco IOS, Juniper Junos, Netscreen load balancers too etc. IMHO makes jumping around CL…

Why is anyone using anything else?

Likely because they haven't seen the light just yet. Or they are lost to the evil forces.

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

#150

Post by mindcrime »

mesrik wrote: post #110
ot wrote: post #85

Earlier quoted context omitted.

> GNU deadline I think you mean readline?

Sure. Browser autocorrect there just tried to be helpful :/

That said, I'm kinda hoping somebody does create a "GNU deadline" project now. I'm curious to see what kind of project it would be.
Post reply on HN