Hacker News Reader

Comment by taeric | Hacker News Reader

I'm curious what OS you are in. Unless I am over a slow tramp connection, it isn't common for me to see any lag in the editor.

And it is amusing that async through a buffer has always been possible. Just far more common for folks to not go that route on round one.

View on HN

Not OP, but macOS here on a MacBook Pro less than a year old. Emacs has always tempted me, but a number of commands take roughly 2-5x the time compared to something like vscode.

Every time I get back to trying out emacs again, I find myself wondering why I would bother with the massive time sink to get it customized to be a sub-par equivalent to another tool that works better for me.

Doom emacs comes the closest for pre-configured setups, but even that isn't halfway to the productivity of what I am trying to replace.

What I really wish is sublime had gone with something other than python for plugins, and was more scriptable overall...

That's why I am 99% likely to move to NeoVim (or LunarVim which steps on it). LuaJIT looks like a very easy script language to learn, with minimal quirks -- at least on the first few looks.

What commands, in particular?

The most distinctive one is when you start typing a chord- it can take up to a good second to populate the command list. Compare this to vscodes command palette which is instant.

I admit that perhaps there is a configurable lag built in (it would make sense to do so) and while there are other examples that I know bother me, this is the one that jumped out straight away. I'd have to dig back in to have more specifics.

I'm not sure what chord menu you mean. :(. I /think/ you are describing "echo-keystrokes", which defaults to one second.

M-x is basically instant for me, though. So, not sure why anything like that would be slow.

Not OP, but for me adding or deleting a character in the middle of a paragraph in a latex doc hangs for maybe .5s or more, often. This is a fairly new phenomenon, never happened 2+ years ago.

That sounds broken. :(

Good luck getting it fixed, if you are still trying. A basic profiler-start, type, profiler-stop, profiler-report can probably pay the blame easily.

macOS.

Can you give me a hint on how to do the async LSP thing then? I never was actually interested in becoming a master in Emacs. ¯\_(ツ)_/¯

Apologies, I meant that async had long been doable in emacs. Compilation mode being a clear example of what that could look like.

That said, most of the newest lsp code is built with the idea that calls out to the server are fast enough to just block.

Thank you for clarifying, much appreciated. <3

Looks like LSP mode is async [1], but I haven't set it up myself. I mostly use Emacs as an org-mode app.

[1] https://emacs-lsp.github.io/lsp-mode/

I'm the same. I do still edit all of my code in emacs, but I grew to dislike most auto complete setups years ago. :(

I sometimes fear it hurts my productivity, but I'm not seeing any real boost in the folks that use them.

Reply on news.ycombinator.com