homebrew-emacsmacport VS coreutils

Run emacs -q (no add-ons loaded) and it should be a lot faster than VS Code. Which means that a library you loaded is the culprit. Things like Doom Emacs are notorious for unexpected slowness since they're not very well put together and load questionable libraries.

In the unlikely case where emacs -q is still slow, use Emacs Mac Port (https://github.com/railwaycat/homebrew-emacsmacport/releases...).

This is at least 2x perceivably faster than VS Code on Mac.

Important note: I learned that apparently not all Emacsen properly support :stipple (despite happily accepting it as a face attribute). Linux/UNIX is safe, emacs-mac supports it on MacOS, but Windows may not at all (untested). Also, terminal emacs does not (to my knowledge) implement :stipple. Let me know how you fare. Update: Pure GTK emacs apparently does display stipples, but incorrectly (as an inverse mask).

I don't use macOS anymore, but the best port I found for speed was https://github.com/railwaycat/homebrew-emacsmacport

There is the code to do just that. Works with emacs-mac and emacs-plus.

There's the "Mac" version, from Mitsuharu Yamamoto or railwaycat. The Mac port works more like Mac than the NextStep port. And it looks like the Mac port does work with C-f4.

Homebrew

You can install emacs-mac by homebrew (see https://github.com/railwaycat/homebrew-emacsmacport). $ brew tap railwaycat/emacsmacport $ brew install emacs-mac This emacs contains mac-win.el. Mac Auto ASCII mode in the mac-win.el automatically selects the most-recently-used ASCII-capable keyboard input source on some occasions: after prefix key (bound in the global keymap) press such as C-x and M-g, and at the start of minibuffer input. This function is very useful. I guess you can read Japanese, please visit Japanese setup page of my website (https://taipapamotohus.com/post/japanese\_setup/).

For what it's worth, the emacs-mac port provides a mac-effective-appearance-change-hook hook to do the same thing as the System appearance change plugin. I use it like this:

Not that it should represent the rubicon of when to/not to rewrite code, but when you do, you do trade one set of bugs for a new set of bugs: https://github.com/uutils/coreutils/issues

Would be interesting to see a a Debian derivative that combines this with the Rust Implementation Of GNU Coreutils.[1] Could be a big win for memory safety and performance.

[1] https://github.com/uutils/coreutils

uutils /coreutils is also a great project. It has many contributors, and it also is a great resource to learn.

You might be interested in this? https://github.com/uutils/coreutils

Already did it. Checkmate, as i believe your people say.

There is already a rust implementation of coreutiils that uses a single binary like BusyBox or toybox. https://github.com/uutils/coreutils

Ah yes, std, that famous crate that is unusable for systems programming. God forbid anyone do any "systems" programming that uses std.