esup VS kakoune

Probably the best way to figure out what's going on at startup time is ESUP (Emacs Start Up Profiler): https://github.com/jschaf/esup You could run it on the old config and the new. Although I suppose the processes may be different enough that there's nothing meaningful to compare.

I agree with you. For startup profiling, use-package-report and https://github.com/jschaf/esup can help too.

A very useful tool for achieving faster startup is esup (https://github.com/jschaf/esup) which times each code block that runs in the emacs startup.

Have you tried running M-x esup with https://github.com/jschaf/esup to see what is taking up the start-up time?

Are you on Emacs 28? Native-comp is enabled by default and it's Just Worked™ for me. Or are you on at least Emacs 27? Emacs 27 added native JSON parsing; stuff like lsp-mode works a lot better now.

(Personally running Emacs 29 built from source on an M1 Pro; everything is instant! Even on my old dumpy i5 machine, everything except startup was pretty snappy, with the exception of startup which took ~4 seconds.)

If it's startup you're concerned about, try the esup[1] package to figure out what's taking so long.

[1]: https://github.com/jschaf/esup

If you're really interested what happens on startup, you can play around with the startup profiler( https://github.com/jschaf/esup ) or similar packages that time the execution of your .emacs.

I used the Emacs Startup Profiler (ESUP) https://github.com/jschaf/esup which identified several culprits in my init files. Removing or deferring the loading of those packages took my startup time from ~15 seconds to about 2.5 seconds. (Still room for improvement!)

GitHub - jschaf/esup: ESUP - Emacs Start Up Profiler

Try out esup

Helix's modal editing is based on Kakoune's modal editing which is like an evolution to Vim's modal editing. You can think of it as being always in selection (visual) mode. https://github.com/mawww/kakoune?tab=readme-ov-file#selectio...

And while it doesn’t use the sam language precisely, I think in the broader “postfix Vi with visual feedback” category Kakoune[1] also warrants mentioning. The command language, in my experience, feels much more logical than that of Vis coming from a blank slate (things might be different if you come from Vim, but even when I used Vim regularly I never used the editing language that much exactly because I could never remember the damn thing).

And having mentioned Kakoune it’d probably be unfair to then not mention Helix[2]. It has a very similar editing language, but it’s a fairly anti-Unix everything-bolted-in affair on the inside (“everything works out of the box” being the advertising take) compared to Kakoune’s Acme-inspired no-scripting scripting (there’s an ex-style command to exec a user program that can then drive the editor over stdio RPC, a set of hooks, and that’s it). So if you’ve come for the Plan 9 feels, I don’t expect Helix to be that appealing. It’s still a good editor, nevertheless.

[1] https://kakoune.org/

[2] https://helix-editor.com/

You can take a look at kakoune. The source code (excluding documentations, test cases, customizations etc.) is less than 40k. It is, IMHO, a show case of a C++ project in use.

> I wonder if the author has ever heard of vis[0]

Yes.

https://github.com/martanne/vis/wiki/Differences-from-Kakoun...

https://github.com/mawww/kakoune/wiki#onboarding

> which imho fulfills far better each one of those premises

Not very motivated for such a harsh critic..

I've been using Vim for years, but if there was one thing I could change, it would be the verb-noun order. The Kakoune[1] editor behaves mostly like Vim, but where Vim has `dw` as "delete word", Kakoune has it backwards: `wd`.

It might sound minor, but by placing the range first, Kakoune can give a preview of what will be changed. The longer or more complicated the command, the more this feature shines.

Strictly better as far as I know. A shame my muscle memory, and all default installations, are still stuck with Vim.

[1] https://kakoune.org/

Helix is a postmodern text editor built in Rust built for the terminal. It is inspired by Kakoune, another Rust based text editor. Helix has got multiple selections, built-in Tree-sitter integration, powerful code manipulation and Language server support.