Correct some typos
This commit is contained in:
parent
d407b3355a
commit
a7e8e50c40
5 changed files with 28 additions and 28 deletions
16
docs/faq.org
16
docs/faq.org
|
@ -134,11 +134,11 @@ Doom had ++four++ *five* goals for its package management system:
|
|||
4. *Organization:* an Emacs configuration grows so quickly, in complexity and
|
||||
size. A clear separation of concerns (configuration of packages from their
|
||||
installation) is more organized.
|
||||
5. *Reproducability:* /This goal hasn't been implemented yet/, but all our work
|
||||
5. *Reproducibility:* /This goal hasn't been implemented yet/, but all our work
|
||||
up until now is aimed at this goal. Emacs is a tumultuous ecosystem; packages
|
||||
break left and right, and we rely on hundreds of them. Eventually, we want
|
||||
package versions to be locked to versions of Doom so that Doom installs are
|
||||
reproducable.
|
||||
reproducible.
|
||||
|
||||
** How does Doom start up so quickly?
|
||||
Doom employs a number of techniques to cut down startup time. Here are its most
|
||||
|
@ -384,7 +384,7 @@ editing in the terminal (without ~-Q~). This also facilitates:
|
|||
for nix-shell users, or to isolate one instance for IRC from an instance for
|
||||
writing code, etc).
|
||||
- Quicker restarting of Emacs, to reload package settings or recover from
|
||||
disasterous errors which can leave Emacs in a broken state.
|
||||
disastrous errors which can leave Emacs in a broken state.
|
||||
- Faster integration with "edit in Emacs" solutions (like [[https://github.com/alpha22jp/atomic-chrome][atomic-chrome]]), and
|
||||
the potential to use them without a running daemon.
|
||||
|
||||
|
@ -466,7 +466,7 @@ public variables/functions (e.g. ~bookmark-default-file~ or
|
|||
~doom--fix-broken-smie-modes-a~, ~+org--babel-lazy-load-library-a~
|
||||
+ ~doom-[-]NAME-fn~ or ~+MODULE-[-]NAME-fn~ :: Indicates an [[https://en.wikipedia.org/wiki/Strategy_pattern][strategy]] function. A
|
||||
good rule of thumb for what makes a strategy function is: is it
|
||||
interchangable? Can it be replaced with another function with a matching
|
||||
interchangeable? Can it be replaced with another function with a matching
|
||||
signature? e.g. ~+lookup-dumb-jump-backend-fn~, ~+magit-display-buffer-fn~,
|
||||
~+workspaces-set-project-action-fn~
|
||||
+ ~abc!~ :: A public Doom "autodef" function or macro. An autodef should always
|
||||
|
@ -746,7 +746,7 @@ consistent with other Emacs functions. For example, word characters are exactly
|
|||
those characters that are matched by the regular expression character class
|
||||
~[:word:]~.
|
||||
|
||||
If you want the underscore to be recognised as word character, you can modify
|
||||
If you want the underscore to be recognized as word character, you can modify
|
||||
its entry in the syntax-table:
|
||||
|
||||
#+BEGIN_SRC emacs-lisp
|
||||
|
@ -1020,8 +1020,8 @@ TL;DR: =ws-butler= is less imposing.
|
|||
Don't be that guy who PRs 99 whitespace adjustments around his one-line
|
||||
contribution. Don't automate this aggressive behavior by attaching
|
||||
~delete-trailing-whitespace~ (or ~whitespace-cleanup~) to ~before-save-hook~. If
|
||||
you have rambunctous colleagues peppering trailing whitespace into your project,
|
||||
you need to have a talk (with wiffle bats, preferrably) rather than play this
|
||||
you have rambunctious colleagues peppering trailing whitespace into your project,
|
||||
you need to have a talk (with wiffle bats, preferably) rather than play this
|
||||
passive-aggressive game of whack-a-mole.
|
||||
|
||||
Here at Doom Inc we believe that operations that mutate entire files should
|
||||
|
@ -1138,7 +1138,7 @@ If neither of these solve your issue, try ~bin/doom doctor~. It will detect a
|
|||
variety of common issues, and may give you some clues as to what is wrong.
|
||||
|
||||
** The frame goes black on MacOS, while in full-screen mode
|
||||
There are known issues with childframes and MacOS's fullscreen mode. There is no
|
||||
There are known issues with childframes and macOS's fullscreen mode. There is no
|
||||
known fix for this. To work around it, you must either:
|
||||
|
||||
1. Avoid MacOS native fullscreen by maximizing Emacs instead,
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue