Live data from Hacker News

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

rahuljuliato.com

161–170 of 294 posts

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

#161
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.

It’s slow, bloated and packed to the brim with “features” you will never need.

There is Only One. En garde!

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

#163

"Is anyone still using emacs?" I'd like to, but there is currently a RAM shortage

By all means go back to the lean, memory-efficient VS Code, then

There is a superior, faster and more efficient alternative just at your fingertips waiting to unleash its magnificent power if you would only dare to dream big.

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

#165
post #154

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.

It annoys me so much to have learned that GTK text fields used to have an Emacs editing mode, which they've hidden behind an unaccessible configuration option, and now it's hopelessly broken in modern GTK version.

I spent a day or so hacking around with kanata[0], which is a kernel level keyboard remapping tool, that lets you define[1] keyboard mapping layers in a similar way you might with QMK firmware. When I hit the control or meta/alt/option key, it activates a layer where Emacs editing keys are emulated using the GTK equivalents. For example, C-a and C-e are mapped to home/end, etc. I preserve my macOS CMD-not-control-key muscle memory this way too.

The only problem is, this is not the behavior I want in terminals or in GNU/Emacs itself. I wrote a small python daemon (managed by a systemd user service) which wakes up whenever the active window changes. Based on this info, I send a message to the TCP server that kanata (also managed by a systemd user service) provides for remote control to switch to the appropriate layer.

[0]: https://github.com/jtroo/kanata

[1]: https://gitlab.com/spudlyo/dotfiles/-/blob/master/kanata/.co...

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

#166

It's nice to hear the emacs terminal emulator has gotten some love, after all the controversy about the nasty language that used to be in its source code, which rms moved out to a separate file after somebody complained. Open source with profanity in comments is statistically better than code without it: https://blog.desdelinux.net/en/open-source-with-profanity-in... https://news.ycombinator.com/item?id=36621699 DonH…

Thanks for this interesting bit of history! Fun little read

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

#167
post #155

Earlier quoted context omitted.

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.

A weird, inscrutable project management tool for the shell written in Perl 4 and Guile Scheme, that the ten people in the world who learned to operate it swear it is the greatest piece of productivity software ever invented.

Notable users: GNU HURD Project (Shipping any day now).

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

#168
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…

> Emacs cursor movement keystrokes are quite widely supported elsewhere too

Yes, even in Codex and Claude Code.

> Those work well also besides shells with Chromium/Chrome/Safari... My only gripe is that Firefox and its derivatives it doesn't work any more

Interesting, my experience is exactly the opposite: I had to finally bite the bullet and migrate to Firefox because Chrome/ium switched to GTK4 which removed key themes support.

(That's OK though, I should've moved off Chrome a long time ago.)

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

#169
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.

43 years for me. Started in 1983 using Gosmacs on a black-and-white CRT terminal. Gosling too was frequently in the terminal room.

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

#170
post #106
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?

I use Lem. It's an "emacs" but not a clone of GNU Emacs. It's written in Common Lisp, extensible in Common Lisp and it's way more performant than GNU Emacs. Obviously less features and plugins but for my needs (writing Lisp code mostly) it's great.
Post reply on HN