Live data from Hacker News

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

rahuljuliato.com

111–120 of 294 posts

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

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

>You won't suddenly find your text editor "upgraded" with tons of new features you never asked for. I never asked for native compilation implemented via the trampoline technique, which increases attack surface (because it causes Emacs to routinely execute files in a known-by-attackers location in my home directory) and makes debugging harder, but I'm stuck with it if I want my Emacs to speak the Wayland protocol (and…

Native compilation is optional as you surely know.

It also has nothing to do with Wayland.

And what's wrong with adding lexical scope!?

I do have some concerns about certain features but the ones listed do work, and work great.

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

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

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

#114
post #28
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…

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?

For your consideration, two Elisp packages I've written that focus on feature discoverability and use: Casual and Anju, both available from MELPA. You can read more about them at the following links: https://github.com/kickingvegas/casual https://github.com/kickingvegas/anju

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

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

>You won't suddenly find your text editor "upgraded" with tons of new features you never asked for. I never asked for native compilation implemented via the trampoline technique, which increases attack surface (because it causes Emacs to routinely execute files in a known-by-attackers location in my home directory) and makes debugging harder, but I'm stuck with it if I want my Emacs to speak the Wayland protocol (and…

Sigh. Don’t be “that guy.”

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

#116

This stuff all looks great, I can't wait to upgrade to 31 and then forget about all of it and just keep using Emacs the same way I have been for the past 20 years, /again/

I'm glad to see that people are working on emacs, as I use it constantly. That said, I personally don't see myself really using any of the stuff highlighted in this article. I've never really been in to advanced auto-complete or tree-sitter type of functionality. Some tasteful syntax highlighting and indentation support is fine but that's about as far as I go. That, org-mode, and magit is about all I use for coding and text editing. I also use notmuch for email.

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

#118

Earlier quoted context omitted.

>You won't suddenly find your text editor "upgraded" with tons of new features you never asked for. I never asked for native compilation implemented via the trampoline technique, which increases attack surface (because it causes Emacs to routinely execute files in a known-by-attackers location in my home directory) and makes debugging harder, but I'm stuck with it if I want my Emacs to speak the Wayland protocol (and…

Native compilation is optional as you surely know. It also has nothing to do with Wayland. And what's wrong with adding lexical scope!? I do have some concerns about certain features but the ones listed do work, and work great.

You can't build an Emacs with Wayland (PGTK) support without native comp. ./configure will complain and refuse to do it.

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

#119
post #5
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…

The two complaints I hear is: 1.Memorizing how to use it has a big learning curve. 2.Wrist pain from pressing button combinations all the time. Otherwise plenty of people still use it and it's great. Just hard to pick up for new users.

WRT point 2, binding the caps-lock key to ctrl helps a lot, or finding a keyboard with the ctrl key to the left of "A".
Post reply on HN