125 lines
3.5 KiB
Markdown
125 lines
3.5 KiB
Markdown
# Configuration
|
|
|
|
## Color Themes
|
|
|
|
Emacs provides a dozen of
|
|
built-in themes you can use out-of-the-box by invoking the `M-x
|
|
load-theme` command.
|
|
|
|
[Zenburn](https://github.com/bbatsov/zenburn-emacs) is the default
|
|
color theme in Prelude, but you can change it at your discretion. Why
|
|
Zenburn? I (and lots of hackers around the world) find it pretty neat
|
|
for some reason. Personally I find the default theme pretty tiresome
|
|
for the eyes, that's why I took that "controversial" decision to
|
|
replace it. You can, of course, easily go back to the default (or
|
|
select another theme entirely).
|
|
|
|
To disable Zenburn just put in your personal config the following
|
|
line:
|
|
|
|
```lisp
|
|
(disable-theme 'zenburn)
|
|
```
|
|
|
|
Or you can use another theme altogether by adding something in `personal/preload` like:
|
|
|
|
```lisp
|
|
(setq prelude-theme 'tango)
|
|
```
|
|
|
|
**Note** To use a non-built-in theme, like [Solarized](https://github.com/bbatsov/zenburn-emacs),
|
|
you'll have to install it from MELPA first by `M-x package-install RET solarized-theme`. Then add
|
|
|
|
``` lisp
|
|
(setq prelude-theme 'solarized-dark)
|
|
```
|
|
in `personal/preload`.
|
|
|
|
Finally, if you don't want any theme at all, you can add this to your
|
|
`personal/preload`:
|
|
|
|
```lisp
|
|
(setq prelude-theme nil)
|
|
```
|
|
|
|
## Personalizing
|
|
|
|
All files you create under the `personal/` directory are yours for
|
|
personalization. There is no single special personal config file --
|
|
any files you create in the `personal/` directory will be loaded in
|
|
lexicographical order. The overall loading precedence is:
|
|
|
|
1. `personal/preload/*`
|
|
2. `core/`
|
|
3. `prelude-modules.el`
|
|
4. `personal/*`
|
|
|
|
#### Personalization Example
|
|
|
|
Suppose you want to configure `go-mode` to autoformat on each save. You
|
|
can create a file in `personal/`, let's call this one
|
|
`config-go-mode.el` and add the following to it.
|
|
|
|
``` emacs-lisp
|
|
(add-hook 'go-mode-hook
|
|
(lambda ()
|
|
(add-hook 'before-save-hook 'gofmt-before-save)
|
|
(setq tab-width 2)))
|
|
```
|
|
|
|
#### Tips
|
|
|
|
**Fork** (instead of cloning) the official Prelude repo and add your
|
|
own touch to it. You're advised to **avoid changing stuff outside of
|
|
the personal folder** to avoid having to deal with git merge conflicts
|
|
in the future.
|
|
|
|
If you'd like to add some auto installation of packages in your
|
|
personal config use the following code:
|
|
|
|
```lisp
|
|
(prelude-require-packages '(some-package some-other-package))
|
|
```
|
|
|
|
If you require just a single package you can also use:
|
|
|
|
```lisp
|
|
(prelude-require-package 'some-package)
|
|
```
|
|
|
|
### Preloading personal config
|
|
|
|
Sometimes you might want to load code before Prelude has started loading. Prelude will automatically preload all
|
|
Emacs Lisp files in your `personal/preload` directory. Note that at this point you can't using anything from
|
|
Prelude, except a few variables like `prelude-dir`, etc (since nothing is yet loaded).
|
|
|
|
### Disabling whitespace-mode
|
|
|
|
Although `whitespace-mode` is awesome, some people might find it too
|
|
intrusive. You can disable it in your
|
|
personal config with the following bit of code:
|
|
|
|
```lisp
|
|
(setq prelude-whitespace nil)
|
|
```
|
|
|
|
If you like `whitespace-mode`, but prefer it to not automatically
|
|
cleanup your file on save, you can disable that behavior by setting
|
|
`prelude-clean-whitespace-on-save` to `nil` in your config file with:
|
|
|
|
```lisp
|
|
(setq prelude-clean-whitespace-on-save nil)
|
|
```
|
|
|
|
The `prelude-clean-whitespace-on-save` setting can also be set on a
|
|
per-file or directory basis by using a file variable or a
|
|
`.dir-locals.el` file.
|
|
|
|
|
|
### Disable flyspell-mode
|
|
|
|
If you're not fond of spellchecking on the fly:
|
|
|
|
```lisp
|
|
(setq prelude-flyspell nil)
|
|
```
|