![]() ![]() emacs file and troubleshooting, see this article. So this doesn't really make sense to me.įor info about the. My ~/Library/Preferences/Aquamacs Emacs/Preferences.el looks like (by default): (load "~/.emacs") ~/Library/Preferences/Aquamacs Emacs/Preferences.el ~/Library/Preferences/Emacs/Preferences.el Library/Preferences/Aquamacs Emacs/Preferences.el Library/Preferences/Emacs/Preferences.el ![]() How can I debug this? Where should I set my custom faces?Īccording to this, preferences should be loaded in the following order: ~/.emacs (deprecated - meaning 'should not be usedįor new installations, but will continue to be supported' - in Aquamacs on OS X)Ĭustomizations saved by request or automatically by Aquamacs in customizations.el My guess is that these options are overridden in some other place. emacs and manually evaluate them, everything works fine. This block seems not to be applied automatically. '(zmacs-region ((t (:background "grey70" :foreground "black"))))) '(mode-line ((t (:background "grey90" :foreground "black")))) '(isearch ((t (:background "yellow4" :foreground "black")))) '(font-lock-warning-face ((t (:foreground "grey50")))) '(font-lock-variable-name-face ((t (:foreground "orange")))) '(font-lock-type-face ((t (:foreground "violet")))) '(font-lock-string-face ((t (:foreground "yellow2")))) '(font-lock-reference-face ((t (:foreground "LightSkyBlue")))) '(font-lock-preprocessor-face ((t (:foreground "SteelBlue")))) '(font-lock-keyword-face ((t (:foreground "red")))) '(font-lock-function-name-face ((t (:foreground "SteelBlue")))) '(font-lock-doc-string-face ((t (:foreground "yellow2")))) '(font-lock-constant-face ((t (:foreground "grey50")))) '(font-lock-comment-face ((t (:foreground "darkgreen")))) '(font-lock-builtin-face ((t (:foreground "grey50")))) '(default ((t (:stipple nil :background "black" :foreground "grey70" :inverse-video nil :box nil :strike-through nil :overline nil :underline nil :slant normal :weight normal :height 140 :width normal :foundry "apple" :family "Monaco")))) emacs file in my home, which contains all my customizations. In these cases, I would recommend the railwaycat brew formula or, respectively.I have a. You can also install pre-built binaries via homebrew or downloaded from the web. For the first question, if you wanted to build your own, just got clone the repo from savannah, or Mitsuharu’s mac port from bitbucket, and follow the instructions therein. If you’re interested, this is a fine way to live (I lived this way myself for almost a decade until my battleship 2011 mbp finally died during the era of the terrible butterfly keyboards). That means that you can try out new features much faster than the slow release schedule, if you want.įor the mac, it’s not hard to go from “macOS with Xcode” to “using a self-built emacs”. On the other hand, the development head is also very usable - at least a couple decades of my own usage has been self-built from the most recent sources, and problems have been very, very rare. The releases are relatively rare, every year or two on the new “fast” schedule, and are supported for a long while. The other question is: build your own latest and greatest, or use a stable package built by someone else? Emacs is a remarkably stable piece of software (seriously I’ve been using it for more than 30 years, and there are lots of people who’ve been using it longer). ![]() For pure functionality on current macOS, I think the mac port has a few niceties that are missing from the ns port, and the cost of being a bit behind the bleeding edge - which brings us to the other question. Both work well, and there are reasons to prefer both. ![]() There is also another version, more recent, that uses different low-level macOS toolkits/frameworks/primitives called the “mac port”. One question is: which version of “make emacs work well under macOS” should I use? There’s a default version that comes with emacs for many years, that also works with GNUStep, thanks called the “ns port”. This is kind of two questions, depending on your circumstances. ![]()
0 Comments
Leave a Reply. |