Emacs config utilizing prelude as a base
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

558 lines
19 KiB

13 years ago
14 years ago
14 years ago
  1. Emacs Prelude
  2. =============
  3. Prelude is an Emacs distribution that aims to enhance the default
  4. Emacs experience. Prelude alters a lot of the default settings,
  5. bundles a plethora of additional packages and adds its own core
  6. library to the mix. The final product offers an easy to use Emacs
  7. configuration for Emacs newcomers and lots of additional power for
  8. Emacs power users.
  9. Prelude is compatible **ONLY with GNU Emacs 24.x**. In general you're
  10. advised to always run Prelude with the latest Emacs - currently
  11. **24.3**.
  12. ## Fast Forward
  13. Assuming you're using an Unix-like OS (`*BSD`, `GNU/Linux`, `OS X`, `Solaris`,
  14. etc), you already have Emacs 24 installed, as well as `git` & `curl` you
  15. can skip the whole manual and just type in your favorite shell the
  16. following command:
  17. ```bash
  18. curl -L http://git.io/epre | sh
  19. ```
  20. You can now power up your Emacs, sit back and enjoy Prelude,
  21. forgetting about the rest of this manual.
  22. There are two environment variables you can use to control the
  23. source repository and the installation directory. To change the
  24. installation directory:
  25. ```bash
  26. export PRELUDE_INSTALL_DIR="$HOME/.emacs.d" && curl -L https://github.com/bbatsov/prelude/raw/master/utils/installer.sh | sh
  27. ```
  28. To change the source repository:
  29. ```bash
  30. export PRELUDE_URL="https://github.com/yourname/prelude.git" && curl -L https://github.com/bbatsov/prelude/raw/master/utils/installer.sh | sh
  31. ```
  32. Note that the installer will back up any existing `.emacs` file or
  33. `.emacs.d` since it will unpack Prelude's code in `.emacs.d`. If
  34. you're doing a manual install make sure you don't have a `.emacs` file
  35. or back up your existing `.emacs.d` directory manually.
  36. Don't forget to adjust your `prelude-modules.el` file once the installation is done.
  37. By default most of the modules that ship with Prelude are not loaded.
  38. ## Installing Emacs 24
  39. Obviously to use the Emacs Prelude you have to install Emacs 24
  40. first. Have a look at the [WikEmacs articles on installing Emacs](http://wikemacs.org/wiki/Installing_Emacs).
  41. ## Installation
  42. ### Automated
  43. You can install **Emacs Prelude** via the command line with either `curl` or
  44. `wget`. Naturally `git` is also required.
  45. #### Via Curl
  46. If you're using `curl` type the following command:
  47. ```bash
  48. curl -L https://github.com/bbatsov/prelude/raw/master/utils/installer.sh | sh
  49. ```
  50. #### Via Wget
  51. If you're using `wget` type:
  52. ```bash
  53. wget --no-check-certificate https://github.com/bbatsov/prelude/raw/master/utils/installer.sh -O - | sh
  54. ```
  55. ### Manual
  56. ```bash
  57. git clone git://github.com/bbatsov/prelude.git path/to/local/repo
  58. ln -s path/to/local/repo ~/.emacs.d
  59. cd ~/.emacs.d
  60. ```
  61. You'd do well to replace `~/.emacs.d` with the value of
  62. `user-emacs-directory` for your OS. You can check the value by doing
  63. `C-h v user-emacs-directory` inside Emacs.
  64. ## Updating Prelude
  65. The update procedure is fairly straightforward and consists of 3 steps:
  66. ### Update all bundled packages
  67. Just run <kbd>M-x package-list-packages RET U x</kbd>. Unfortunately this step cannot be automated.
  68. ### Update Prelude's code
  69. ```bash
  70. cd path/to/prelude/installation
  71. git pull
  72. ```
  73. The `path/to/prelude/installation` is usually `~/.emacs.d` (at least
  74. on Unix systems).
  75. Alternatively you can run <kbd>M-x prelude-update</kbd> from Emacs itself.
  76. ### Restart Prelude
  77. It's generally a good idea to stop Emacs after you do the update. The
  78. next time Prelude starts it will install any new dependencies (if
  79. there are such).
  80. ## Enabling additional modules
  81. By default most of the modules that ship with Prelude are not loaded.
  82. ```lisp
  83. ;;; Uncomment the modules you'd like to use and restart Prelude afterwards
  84. (require 'prelude-c)
  85. ;; (require 'prelude-clojure)
  86. ;; (require 'prelude-coffee)
  87. ;; (require 'prelude-common-lisp)
  88. ;; (require 'prelude-css)
  89. (require 'prelude-emacs-lisp)
  90. (require 'prelude-erc)
  91. ;; (require 'prelude-erlang)
  92. ;; (require 'prelude-haskell)
  93. (require 'prelude-js)
  94. ;; (require 'prelude-latex)
  95. (require 'prelude-lisp)
  96. ;; (require 'prelude-markdown)
  97. ;; (require 'prelude-mediawiki)
  98. (require 'prelude-org)
  99. (require 'prelude-perl)
  100. ;; (require 'prelude-python)
  101. ;; (require 'prelude-ruby)
  102. ;; (require 'prelude-scala)
  103. (require 'prelude-scheme)
  104. ;; (require 'prelude-scss)
  105. ;; (require 'prelude-web)
  106. (require 'prelude-xml)
  107. ```
  108. You'll need to adjust your `prelude-modules.el` file once the
  109. installation is done. If you are doing a manual install then you first
  110. need to copy the `prelude-modules.el` available in the sample
  111. directory to the root of `path/to/prelude/installation` and then
  112. adjust that one.
  113. After you've uncommented a module you should either restart Emacs or evaluate the module
  114. `require` expression with <kbd>C-x C-e</kbd>.
  115. ## Running
  116. Nothing fancy here. Just start Emacs as usual. Personally I run Emacs
  117. in daemon mode:
  118. ```bash
  119. emacs --daemon
  120. ```
  121. Afterwards I connect to the server with either a terminal or a GUI
  122. client like this:
  123. ```bash
  124. emacsclient -t
  125. emacsclient -c
  126. ```
  127. You'd probably do well to put a few aliases in your `.zshrc` (or
  128. `.bashrc`):
  129. ```bash
  130. alias e=emacsclient -t
  131. alias ec=emacsclient -c
  132. alias vim=emacsclient -t
  133. alias vi=emacsclient -t
  134. ```
  135. The last two aliases are helpful if you're used to editing files from
  136. the command line using `vi(m)`.
  137. ## Getting to know Prelude
  138. Certainly the best way to understand how Prelude enhances the default
  139. Emacs experience is to peruse Prelude's source code (which is
  140. obviously written in Emacs Lisp). Understanding the code is not
  141. necessary of course. Prelude includes a `prelude-mode` minor Emacs mode
  142. which collects some of the additional functionality added by
  143. Prelude. It also adds an additional keymap that binds many of those
  144. extensions to keybindings.
  145. ### Keymap
  146. #### Global
  147. Keybinding | Description
  148. -------------------|------------------------------------------------------------
  149. <kbd>C-M-h</kbd> | Kill the previous word(`backward-kill-word`). (as in Bash/Zsh)
  150. <kbd>C-x \\</kbd> | `align-regexp`
  151. <kbd>C-+</kbd> | Increase font size(`text-scale-increase`).
  152. <kbd>C--</kbd> | Decrease font size(`text-scale-decrease`).
  153. <kbd>C-x O</kbd> | Go back to previous window (the inverse of `other-window` (`C-x o`)).
  154. <kbd>C-^</kbd> | Join two lines into one(`prelude-top-join-line`).
  155. <kbd>C-x p</kbd> | Start `proced` (manage processes from Emacs; works only in Linux).
  156. <kbd>C-x m</kbd> | Start `eshell`.
  157. <kbd>C-x M-m</kbd> | Start your default shell.
  158. <kbd>C-x C-m</kbd> | Alias for `M-x`.
  159. <kbd>C-h A</kbd> | Run `apropos` (search in all Emacs symbols).
  160. <kbd>M-/</kbd> | Run `hippie-expand` (a replacement for the default `dabbrev-expand`).
  161. <kbd>C-x C-b</kbd> | Open `ibuffer` (a replacement for the default `buffer-list`).
  162. <kbd>F11</kbd> | Make the window full screen.
  163. <kbd>F12</kbd> | Toggle the Emacs menu bar.
  164. <kbd>C-x g</kbd> | Open Magit's status buffer.
  165. <kbd>C-=</kbd> | Run `expand-region` (incremental text selection).
  166. <kbd>C-a</kbd> | Run `prelude-move-beginning-of-line`. Read [this](http://emacsredux.com/blog/2013/05/22/smarter-navigation-to-the-beginning-of-a-line/) for details.
  167. #### Prelude Mode
  168. Keybinding | Description
  169. -------------------|------------------------------------------------------------
  170. <kbd>C-c o</kbd> | Open the currently visited file with an external program.
  171. <kbd>C-c i</kbd> | Search for a symbol, only for buffers that contain code
  172. <kbd>C-c g</kbd> | Search in Google for the thing under point (or an interactive query).
  173. <kbd>C-c G</kbd> | Search in GitHub for the thing under point (or an interactive query).
  174. <kbd>C-c y</kbd> | Search in YouTube for the thing under point (or an interactive query).
  175. <kbd>C-S-RET</kbd> or <kbd>M-o</kbd> | Insert an empty line above the current line and indent it properly
  176. <kbd>S-RET</kbd> or <kbd>M-O</kbd> | Insert an empty line and indent it properly (as in most IDEs).
  177. <kbd>C-S-up</kbd> or <kbd>M-S-up</kbd> | Move the current line or region up.
  178. <kbd>C-S-down</kbd> or <kbd>M-S-down</kbd>| Move the current line or region down.
  179. <kbd>C-c n</kbd> | Fix indentation in buffer and strip whitespace.
  180. <kbd>C-c f</kbd> | Open recently visited file.
  181. <kbd>C-M-\\</kbd> | Indent region (if selected) or the entire buffer.
  182. <kbd>C-c u</kbd> | Open URL in your default browser.
  183. <kbd>C-c e</kbd> | Eval a bit of Emacs Lisp code and replace it with its result.
  184. <kbd>C-c s</kbd> | Swap two active windows.
  185. <kbd>C-c d</kbd> | Duplicate the current line (or region).
  186. <kbd>C-c M-d</kbd> | Duplicate and comment the current line (or region).
  187. <kbd>C-c r</kbd> | Rename the currently visited file and buffer.
  188. <kbd>C-c t</kbd> | Open a terminal emulator (`ansi-term`).
  189. <kbd>C-c k</kbd> | Kill all open buffers except the one you're currently in.
  190. <kbd>C-c h</kbd> | Open Helm (a useful means of navigating your buffers and project files).
  191. <kbd>C-c +</kbd> | Increment integer at point.
  192. <kbd>C-c -</kbd> | Decrement integer at point.
  193. <kbd>Super-r</kbd> | Recent files
  194. <kbd>Super-x</kbd> | Expand region
  195. <kbd>Super-j</kbd> | Join lines
  196. <kbd>Super-k</kbd> | Kill whole line
  197. <kbd>Super-m m</kbd> | Magit status
  198. <kbd>Super-m l</kbd> | Magit log
  199. <kbd>Super-m f</kbd> | Magit file log
  200. <kbd>Super-m b</kbd> | Magit blame mode
  201. <kbd>Super-o</kbd> | Open line above current line
  202. #### OSX modifier keys
  203. Prelude does not mess by default with the standard mapping of `Command` (to `Super`) and `Option` (to `Meta`).
  204. If you want to swap them add this to your personal config:
  205. ```lisp
  206. (setq mac-command-modifier 'meta)
  207. (setq mac-option-modifier 'super)
  208. ```
  209. You can also temporarily swap them with `C-c w` (`M-x prelude-swap-meta-and-super`).
  210. #### Projectile
  211. Here's a list of functionality provided by [Projectile](https://github.com/bbatsov/projectile):
  212. Keybinding | Description
  213. -------------------|------------------------------------------------------------
  214. <kbd>C-c p f</kbd> | Display a list of all files in the project. With a prefix argument it will clear the cache first.
  215. <kbd>C-c p d</kbd> | Display a list of all directories in the project. With a prefix argument it will clear the cache first.
  216. <kbd>C-c p T</kbd> | Display a list of all test files(specs, features, etc) in the project.
  217. <kbd>C-c p g</kbd> | Run grep on the files in the project.
  218. <kbd>C-c p b</kbd> | Display a list of all project buffers currently open.
  219. <kbd>C-c p o</kbd> | Runs `multi-occur` on all project buffers currently open.
  220. <kbd>C-c p r</kbd> | Runs interactive query-replace on all files in the projects.
  221. <kbd>C-c p i</kbd> | Invalidates the project cache (if existing).
  222. <kbd>C-c p R</kbd> | Regenerates the projects `TAGS` file.
  223. <kbd>C-c p k</kbd> | Kills all project buffers.
  224. <kbd>C-c p D</kbd> | Opens the root of the project in `dired`.
  225. <kbd>C-c p e</kbd> | Shows a list of recently visited project files.
  226. <kbd>C-c p a</kbd> | Runs `ack` on the project. Requires the presence of `ack-and-a-half`.
  227. <kbd>C-c p c</kbd> | Runs a standard compilation command for your type of project.
  228. <kbd>C-c p p</kbd> | Runs a standard test command for your type of project.
  229. <kbd>C-c p z</kbd> | Adds the currently visited to the cache.
  230. <kbd>C-c p s</kbd> | Display a list of known projects you can switch to.
  231. Prelude adds some extra keybindings:
  232. Keybinding | Command
  233. -------------------|------------------------------------------------------------
  234. <kbd>Super-f</kbd> | Find file in project
  235. <kbd>Super-d</kbd> | Find directory in project
  236. <kbd>Super-g</kbd> | Run grep on project
  237. <kbd>Super-p</kbd> | Switch projects
  238. If you ever forget any of Projectile's keybindings just do a:
  239. <kbd>C-c p C-h</kbd>
  240. #### Key-chords
  241. Keybinding | Description
  242. -------------------|----------------------------------------------
  243. <kbd>jj</kbd> | Jump to the beginning of a word(`ace-jump-word-mode`)
  244. <kbd>jk</kbd> | Jump to a character(`ace-jump-char-mode`)
  245. <kbd>jl</kbd> | Jump to the beginning of a line(`ace-jump-line-mode`)
  246. <kbd>JJ</kbd> | Jump back to previous buffer(`prelude-switch-to-previous-buffer`)
  247. <kbd>uu</kbd> | View edits as a tree(`undo-tree-visualize`)
  248. ##### Disabling key-chords
  249. In some cases you may not want to have a key-chord that is defined by prelude,
  250. in which case you can disable the binding in your `personal.el` file by setting
  251. its command to `nil`. For example, to disable the `jj` key-chord add the
  252. following line:
  253. ```lisp
  254. (key-chord-define-global "jj" nil)
  255. ```
  256. If you're an `evil-mode` user you'll probably do well to disable `key-chord-mode` altogether:
  257. ```lisp
  258. (key-chord-mode -1)
  259. ```
  260. ## Automatic package installation
  261. The default Prelude installation comes with a bare minimum of
  262. functionality. It will however install add-ons for various programming
  263. languages and frameworks on demand. For instance - if you try to open
  264. a `.clj` file `clojure-mode`, `nrepl.el` and prelude's enhanced Lisp
  265. configuration will be installed automatically for you.
  266. You can, of course, install anything you wish manually as well.
  267. ### Color Themes
  268. Emacs 24 ships with a new theming facility that effectively renders
  269. the old color-theme package obsolete. Emacs 24 provides a dozen of
  270. built-in themes you can use out-of-the-box by invoking the `M-x
  271. load-theme` command.
  272. [Zenburn](https://github.com/bbatsov/zenburn-emacs) is the default color theme in Prelude, but you can change it
  273. at your discretion. Why Zenburn? I (and lots of hackers around the
  274. world) find it pretty neat for some reason. Personally I find the
  275. default theme pretty tiresome for the eyes, that's why I took that
  276. "controversial" decision to replace it. You can, of course, easily go
  277. back to the default (or select another theme entirely).
  278. To disable Zenburn just put in your personal config the following
  279. line:
  280. ```lisp
  281. (disable-theme 'zenburn)
  282. ```
  283. Or you can use another theme altogether by adding something like:
  284. ```lisp
  285. (load-theme 'solarized-dark t)
  286. ```
  287. **P.S.** Solarized is not available by default - you'll have to
  288. install it from MELPA first (`M-x package-install RET
  289. solarized-theme`).
  290. ### Personalizing
  291. Fork the official Prelude repo and add your own touch to it. You're advised to avoid changing stuff outside of the
  292. personal folder to avoid having to deal with git merge conflicts in the future.
  293. If you'd like to add some auto installation of packages in your
  294. personal config use the following code:
  295. ```lisp
  296. (prelude-require-packages '(some-package some-other-package))
  297. ```
  298. If you require just a single package you can also use:
  299. ```lisp
  300. (prelude-require-package 'some-package)
  301. ```
  302. #### Disabling whitespace-mode
  303. Although `whitespace-mode` is awesome some people might find it too
  304. intrusive. You can disable it in your
  305. personal config with the following bit of code:
  306. ```lisp
  307. (setq prelude-whitespace nil)
  308. ```
  309. If you like `whitespace-mode` but prefer it to not automatically
  310. cleanup your file on save, you can disable that behavior by setting
  311. prelude-clean-whitespace-on-save to nil in your config file with:
  312. ```lisp
  313. (setq prelude-clean-whitespace-on-save nil)
  314. ```
  315. The prelude-clean-whitespace-on-save setting can also be set on a
  316. per-file or directory basis by using a file variable or a
  317. .dir-locals.el file.
  318. #### Disable flyspell-mode
  319. If you're not fond of spellchecking on the fly:
  320. ```lisp
  321. (setq prelude-flyspell nil)
  322. ```
  323. ## Caveats & Pitfalls
  324. ### Updating bundled packages
  325. Currently there is no Emacs Lisp API for updating packages, so you'll
  326. have to update manually the packages that came with Prelude from time
  327. to time.
  328. `M-x package-list-packages RET U x`
  329. Generally it's a good idea to do a package update before running
  330. `prelude-update`, since the latest Prelude code might depend on newer
  331. versions of the bundled packages than you would currently have
  332. installed.
  333. ### Problems with flyspell-mode
  334. Prelude makes heavy use of the flyspell-mode package for spell
  335. checking of various things. The proper operation of flyspell depends
  336. on the presence of the `aspell` program and an `en` dictionary on your
  337. system. You can install `aspell` and the dictionary on OS X with
  338. `homebrew` like this:
  339. ```bash
  340. brew install aspell --with-lang=en
  341. ```
  342. On Linux distros - just use your distro's package manager.
  343. ### Ugly colors in the terminal Emacs version
  344. If your Emacs looks considerably uglier in a terminal (compared to the
  345. GUI version) try adding this to your `.bashrc` or `.zshrc`:
  346. ```bash
  347. export TERM=xterm-256color
  348. ```
  349. Source the `.bashrc` file and start Emacs again.
  350. ### MELPA error on initial startup
  351. If you get some http connection error related to the MELPA repo
  352. just do a manual `M-x package-refresh-contents` and restart Emacs
  353. afterwards.
  354. ### No arrow navigation in editor buffers
  355. This is not a bug - it's a feature! I firmly believe that the one true
  356. way to use Emacs is by using it the way it was intended to be used (as
  357. far as navigation is concerned at least). That's why I've disabled all
  358. movement commands with arrows (and keys like page up, page down, etc) - to prevent you from being tempted to
  359. use them.
  360. If you'd still like to use the arrow keys just invoke `M-x
  361. guru-mode` to enable them for the duration of your
  362. current Emacs session or add the following snippet to your
  363. personal Emacs customization to enable them permanently:
  364. ```lisp
  365. (setq prelude-guru nil)
  366. ```
  367. ### Customized C-a behavior
  368. Prelude overrides `C-a` to behave as described
  369. [here](http://emacsredux.com/blog/2013/05/22/smarter-navigation-to-the-beginning-of-a-line/). If
  370. you don't like that simply add this to your personal config:
  371. ```lisp
  372. (global-set-key [remap move-beginning-of-line]
  373. 'move-beginning-of-line)
  374. ```
  375. ### Poor ido matching performance on large datasets
  376. Prelude swaps the default `ido` flex matching with the more powerful
  377. [ido-flx](https://github.com/lewang/flx).
  378. The sorting algorithm `flx` uses is more complex, but yields better results.
  379. On slower machines, it may be necessary to lower `flx-ido-threshhold` to
  380. ensure a smooth experience.
  381. ```lisp
  382. (setq flx-ido-threshhold 1000)
  383. ```
  384. You can always disable the improved sorting algorithm all together like this:
  385. ```lisp
  386. (flx-ido-mode -1)
  387. ```
  388. ### Windows compatibility
  389. While everything in Prelude should work fine in Windows, I test it only
  390. with Linux & OSX, so there are Windows related problems from time to
  391. time. This situation will probably improve over time.
  392. ## Share the knowledge
  393. [WikEmacs](http://wikemacs.org) collects useful resources for working
  394. with GNU Emacs. Please, take the time to peruse and improve them as
  395. you accumulate knowledge about Emacs. Prelude makes this especially
  396. easy, since it bundles
  397. [MediaWiki support](http://wikemacs.org/wiki/Mediawiki.el) + the
  398. settings required to access WikEmacs right away.
  399. ## Known issues
  400. Check out the project's
  401. [issue list](https://github.com/bbatsov/prelude/issues?sort=created&direction=desc&state=open)
  402. a list of unresolved issues. By the way - feel free to fix any of them
  403. and send me a pull request. :-)
  404. ## Support
  405. Support is available via the Prelude Google Group <emacs-prelude@googlegroups.com>.
  406. ## Contributors
  407. Here's a [list](https://github.com/bbatsov/prelude/contributors) of all the people who have contributed to the
  408. development of Emacs Prelude.
  409. ## Bugs & Improvements
  410. Bug reports and suggestions for improvements are always
  411. welcome. GitHub pull requests are even better! :-)
  412. Cheers,<br/>
  413. [Bozhidar](https://twitter.com/bbatsov)