homebrew-emacsmacport VS dot-emacs

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:

For example, I don't know what "vertico, consult, embark, marginalia, and orderless" is exactly, they're not part of my setup and I guess I don't want them to interfere with it.

You can find further optimizations on https://github.com/novoid/dot-emacs/blob/master/config.org when searching for "mode-line".

You're looking for org-expiry and its (org-expiry-insinuate) as you can see in my config: https://github.com/novoid/dot-emacs/blob/master/config.org

You don't have to repeat yourself; it is more about how you write. Literate programming lets you mix different languages as well as text and the code. Check for example Karl Voits. The only remark I can make is that some defvars don't need the comments, since they are written as self-documenting code. For example, 'large-file-warning-threshold' certainly does not need a comment which basically repeats what the name says, but that is not so unusual to see even amongst programmers sometimes.

For the very same reason, I started to use hydras: https://github.com/abo-abo/hydra - see my config at https://github.com/novoid/dot-emacs/blob/master/config.org

The same configuration using Emacs 27.1 also does not have this weird behavior.

Maybe somebody has an idea what I might change in my large setup in order to get rid of this issue ...

For linking to contacts, I started to use a custom link contact: which I don't use any more since I've found org-super-links which enables me to link to any heading quite fine including contacts.

My personal notes on any task or project are way more verbose than the information curated in shared business environments. I therefore invest work and keep a local Orgdown structure and sync a subset of information manually. I define custom links to Jira, emails, and all other external sources to keep links from my Orgdown files to everything else. This way, my only truth is within my personal knowledge management which simplifies search.

My personal approach is a static list of Orgdown files within a single directory (with very few exceptions) and a manually curated list of agenda files.