homebrew-emacsmacport VS homebrew-core

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:

$ brew info eza ==> eza: stable 0.18.13 (bottled) Modern, maintained replacement for ls https://github.com/eza-community/eza Not installed From: https://github.com/Homebrew/homebrew-core/blob/HEAD/Formula/e/eza.rb License: MIT ==> Dependencies Build: pandoc ✘, pkg-config ✔, rust ✘ Required: libgit2 ✘ ==> Analytics install: 12,792 (30 days), 38,295 (90 days), 68,375 (365 days) install-on-request: 12,790 (30 days), 38,293 (90 days), 68,375 (365 days) build-error: 0 (30 days)

Is disabling the compromised repo the typical GitHub policy? My concern is there are monorepos used by package managers, like brew, that are a collection of thousands of projects [1]. These monorepos seem like a prime target for attack and if GitHub disables one because a malicious commit was merged then you've taken down an entire ecosystem.

[1] https://github.com/Homebrew/homebrew-core

> Correct. Though we do not appear to be affected, this revert was done out of an abundance of caution.

[1] https://github.com/Homebrew/homebrew-core/pull/167512

> right, but now you know even less about your setup when you some roadblock

This is the same with a binary though. And with homebrew, you can't follow patches or flags used or if they change.

- https://github.com/Homebrew/homebrew-core/blob/c964ad7fa53ad...

definitely be careful about using fortune in a corporate environment or public space if you don't know what dat files you are using or you might just get an extremely unwelcome surprise.

I was practicing a presentation and used to use "fortune" all the time. I forget exactly what it output but I remember being absolutely mortified about what could have happened if that had popped up during an internal company tech talk.

Kudos to brew for keeping unsuspecting people safe

https://github.com/Homebrew/homebrew-core/commit/3fb3c4c3e55...

I'm sorry to be asking this as I find it a bit silly, but it's blocking my PR [3], so could a few of you star the project on Github [1] to get my PR to run?

[1] https://github.com/laktak/chkbit-py

[2] https://brew.sh

[3] https://github.com/Homebrew/homebrew-core/pull/160018