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.

440 lines
15 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 https://github.com/bbatsov/prelude/raw/master/utils/installer.sh | 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:
  66. ```bash
  67. $ cd path/to/prelude/installation
  68. $ git pull
  69. ```
  70. The `path/to/prelude/installation` is usually `~/.emacs.d` (at least
  71. on Unix systems).
  72. Alternatively you can run <kbd>M-x prelude-update</kbd> from Emacs itself.
  73. It's generally a good idea to stop Emacs before you do the update. The
  74. next time Prelude starts it will install any new dependencies (if
  75. there are such).
  76. ## Enabling additional modules
  77. By default most of the modules that ship with Prelude are not loaded.
  78. ```lisp
  79. ;;; Uncomment the modules you'd like to use and restart Prelude afterwards
  80. (require 'prelude-c)
  81. ;; (require 'prelude-clojure)
  82. ;; (require 'prelude-coffee)
  83. ;; (require 'prelude-common-lisp)
  84. ;; (require 'prelude-css)
  85. (require 'prelude-emacs-lisp)
  86. (require 'prelude-erc)
  87. ;; (require 'prelude-erlang)
  88. ;; (require 'prelude-haskell)
  89. (require 'prelude-js)
  90. ;; (require 'prelude-latex)
  91. (require 'prelude-lisp)
  92. ;; (require 'prelude-markdown)
  93. ;; (require 'prelude-mediawiki)
  94. (require 'prelude-org)
  95. (require 'prelude-perl)
  96. ;; (require 'prelude-python)
  97. ;; (require 'prelude-ruby)
  98. ;; (require 'prelude-scala)
  99. (require 'prelude-scheme)
  100. ;; (require 'prelude-scss)
  101. (require 'prelude-xml)
  102. ```
  103. You'll need to adjust your `prelude-modules.el` file once the
  104. installation is done. If you are doing a manual install then you first
  105. need to copy the `prelude-modules.el` available in the sample
  106. directory to the root of `path/to/prelude/installation` and then
  107. adjust that one.
  108. After you've uncommented a module you should either restart Emacs or evaluate the module
  109. `require` expression with <kbd>C-x C-e</kbd>.
  110. ## Running
  111. Nothing fancy here. Just start Emacs as usual. Personally I run Emacs
  112. in daemon mode:
  113. ```bash
  114. $ emacs --daemon
  115. ```
  116. Afterwards I connect to the server with either a terminal or a GUI
  117. client like this:
  118. ```bash
  119. $ emacsclient -t
  120. $ emacsclient -c
  121. ```
  122. You'd probably do well to put a few aliases in your `.zshrc` (or
  123. `.bashrc`):
  124. ```bash
  125. alias e=emacsclient -t
  126. alias ec=emacsclient -c
  127. alias vim=emacsclient -t
  128. alias vi=emacsclient -t
  129. ```
  130. The last two aliases are helpful if you're used to editing files from
  131. the command line using `vi(m)`.
  132. ## Getting to know Prelude
  133. Certainly the best way to understand how Prelude enhances the default
  134. Emacs experience is to peruse Prelude's source code (which is
  135. obviously written in Emacs Lisp). Understanding the code is not
  136. necessary of course. Prelude includes a `prelude-mode` minor Emacs mode
  137. which collects some of the additional functionality added by
  138. Prelude. It also adds an additional keymap that binds many of those
  139. extensions to keybindings.
  140. ### Keymap
  141. #### Global
  142. Keybinding | Description
  143. -------------------|------------------------------------------------------------
  144. <kbd>C-M-h</kbd> | Kill the previous word(`backward-kill-word`). (as in Bash/Zsh)
  145. <kbd>C-x \\</kbd> | `align-regexp`
  146. <kbd>C-+</kbd> | Increase font size(`text-scale-increase`).
  147. <kbd>C--</kbd> | Decrease font size(`text-scale-decrease`).
  148. <kbd>C-x O</kbd> | Go back to previous window (the inverse of `other-window` (`C-x o`)).
  149. <kbd>C-x ^</kbd> | Join two lines into one(`join-line`).
  150. <kbd>C-x p</kbd> | Start `proced` (manage processes from Emacs; works only in Linux).
  151. <kbd>C-x m</kbd> | Start `eshell`.
  152. <kbd>C-x M-m</kbd> | Start your default shell.
  153. <kbd>C-x C-m</kbd> | Alias for `M-x`.
  154. <kbd>C-h A</kbd> | Run `apropos` (search in all Emacs symbols).
  155. <kbd>M-\\</kbd> | Run `hippie-expand` (a replacement for the default `dabbrev-expand`).
  156. <kbd>C-x C-b</kbd> | Open `ibuffer` (a replacement for the default `buffer-list`).
  157. <kbd>F12</kbd> | Toggle the Emacs menu bar.
  158. <kbd>C-x g</kbd> | Open Magit's status buffer.
  159. <kbd>C-=</kbd> | Run `expand-region` (incremental text selection).
  160. #### Prelude Mode
  161. Keybinding | Description
  162. -------------------|------------------------------------------------------------
  163. <kbd>C-c o</kbd> | Open the currently visited file with an external program.
  164. <kbd>C-c g</kbd> | Search in Google for the thing under point (or an interactive query).
  165. <kbd>C-S-RET</kbd> | Insert an empty line above the current line and indent it properly
  166. <kbd>S-RET</kbd> | Insert an empty line and indent it properly (as in most IDEs).
  167. <kbd>C-S-up</kbd> | Move the current line up.
  168. <kbd>C-S-down</kbd> | Move the current line down.
  169. <kbd>C-c n</kbd> | Fix indentation in buffer and strip whitespace.
  170. <kbd>C-c f</kbd> | Open recently visited file.
  171. <kbd>C-M-\\</kbd> | Indent region (if selected) or the entire buffer.
  172. <kbd>C-c u</kbd> | Open URL in your default browser.
  173. <kbd>C-c e</kbd> | Eval a bit of Emacs Lisp code and replace it with its result.
  174. <kbd>C-c s</kbd> | Swap two active windows.
  175. <kbd>C-c d</kbd> | Duplicate the current line (or region).
  176. <kbd>C-c r</kbd> | Rename the currently visited file and buffer.
  177. <kbd>C-c t</kbd> | Open a terminal emulator (`ansi-term`).
  178. <kbd>C-c k</kbd> | Kill all open buffers except the one you're currently in.
  179. <kbd>C-c h</kbd> | Open Helm (a useful means of navigating your buffers and project files).
  180. #### Projectile
  181. Here's a list of functionality provided by [Projectile](https://github.com/bbatsov/projectile):
  182. Keybinding | Description
  183. -------------------|------------------------------------------------------------
  184. <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.
  185. <kbd>C-c p T</kbd> | Display a list of all test files(specs, features, etc) in the project.
  186. <kbd>C-c p g</kbd> | Run grep on the files in the project.
  187. <kbd>C-c p b</kbd> | Display a list of all project buffers currently open.
  188. <kbd>C-c p o</kbd> | Runs `multi-occur` on all project buffers currently open.
  189. <kbd>C-c p r</kbd> | Runs interactive query-replace on all files in the projects.
  190. <kbd>C-c p i</kbd> | Invalidates the project cache (if existing).
  191. <kbd>C-c p R</kbd> | Regenerates the projects `TAGS` file.
  192. <kbd>C-c p k</kbd> | Kills all project buffers.
  193. <kbd>C-c p d</kbd> | Opens the root of the project in `dired`.
  194. <kbd>C-c p e</kbd> | Shows a list of recently visited project files.
  195. <kbd>C-c p a</kbd> | Runs `ack` on the project. Requires the presence of `ack-and-a-half`.
  196. <kbd>C-c p l</kbd> | Runs a standard compilation command for your type of project.
  197. <kbd>C-c p p</kbd> | Runs a standard test command for your type of project.
  198. <kbd>C-c p z</kbd> | Adds the currently visited to the cache.
  199. <kbd>C-c p s</kbd> | Display a list of known projects you can switch to.
  200. If you ever forget any of Projectile's keybindings just do a:
  201. <kbd>C-c p C-h</kbd>
  202. #### Key-chords
  203. Keybinding | Description
  204. -------------------|----------------------------------------------
  205. <kbd>jj</kbd> | Jump to the beginning of a word(`ace-jump-word-mode`)
  206. <kbd>jk</kbd> | Jump to a character(`ace-jump-char-mode`)
  207. <kbd>jl</kbd> | Jump to the beginning of a line(`ace-jump-line-mode`)
  208. <kbd>JJ</kbd> | Jump back to previous buffer(`prelude-switch-to-previous-buffer`)
  209. <kbd>uu</kbd> | View edits as a tree(`undo-tree-visualize`)
  210. ### Automatic package installation
  211. The default Prelude installation comes with a bare minimum of
  212. functionality. It will however install add-ons for various programming
  213. languages and frameworks on demand. For instance - if you try to open
  214. a `.clj` file `clojure-mode`, `nrepl.el` and prelude's enhanced Lisp
  215. configuration will be installed automatically for you.
  216. You can, of course, install anything you wish manually as well.
  217. ### Color Themes
  218. Emacs 24 ships with a new theming facility that effectively renders
  219. the old color-theme package obsolete. Emacs 24 provides a dozen of
  220. built-in themes you can use out-of-the-box by invoking the `M-x
  221. load-theme` command.
  222. [Zenburn](https://github.com/bbatsov/zenburn-emacs) is the default color theme in Prelude, but you can change it
  223. at your discretion. Why Zenburn? I (and lots of hackers around the
  224. world) find it pretty neat for some reason. Personally I find the
  225. default theme pretty tiresome for the eyes, that's why I took that
  226. "controversial" decision to replace it. You can, of course, easily go
  227. back to the default (or select another theme entirely).
  228. To disable Zenburn just put in your personal config the following
  229. line:
  230. ```lisp
  231. (disable-theme 'zenburn)
  232. ```
  233. Or you can use another theme altogether by adding something like:
  234. ```lisp
  235. (load-theme 'solarized-dark t)
  236. ```
  237. P.S. Solarized is not available by default - you'll have to install it from MELPA first.
  238. ### Personalizing
  239. Fork the official Prelude repo and add your own touch to it. You're advised to avoid changing stuff outside of the
  240. personal folder to avoid having to deal with git merge conflicts in the future.
  241. If you'd like to add some auto installation of packages in your
  242. personal config use the following code:
  243. ```lisp
  244. (prelude-ensure-module-deps '(some-package some-other-package))
  245. ```
  246. #### Disabling whitespace-mode
  247. Although `whitespace-mode` is awesome some people might find it too
  248. intrusive. You can disable it in your
  249. personal config with the following bit of code:
  250. ```lisp
  251. (setq prelude-whitespace nil)
  252. ```
  253. If you like `whitespace-mode` but prefer it to not automatically
  254. cleanup your file on save, you can disable that behavior by setting
  255. prelude-clean-whitespace-on-save to nil in your config file with:
  256. ```lisp
  257. (setq prelude-clean-whitespace-on-save nil)
  258. ```
  259. The prelude-clean-whitespace-on-save setting can also be set on a
  260. per-file or directory basis by using a file variable or a
  261. .dir-locals.el file.
  262. #### Disable flyspell-mode
  263. If you're not fond of spellchecking on the fly:
  264. ```lisp
  265. (setq prelude-flyspell nil)
  266. ```
  267. ## Caveats & Pitfalls
  268. ### Problems with flyspell-mode
  269. Prelude makes heavy use of the flyspell-mode package for spell
  270. checking of various things. The proper operation of flyspell depends
  271. on the presence of the `aspell` program and an `en` dictionary on your
  272. system. You can install `aspell` and the dictionary on OS X with
  273. `homebrew` like this:
  274. ```bash
  275. $ brew install aspell --with-lang=en
  276. ```
  277. On Linux distros - just use your distro's package manager.
  278. ### Ugly colors in the terminal Emacs version
  279. If your Emacs looks considerably uglier in a terminal (compared to the
  280. GUI version) try adding this to your `.bashrc` or `.zshrc`:
  281. ```bash
  282. $ export TERM=xterm-256color
  283. ```
  284. Source the `.bashrc` file and start Emacs again.
  285. ### MELPA error on initial startup
  286. If you get some http connection error related to the MELPA repo
  287. just do a manual `M-x package-refresh-contents` and restart Emacs
  288. afterwards.
  289. ### No arrow navigation in editor buffers
  290. This is not a bug - it's a feature! I firmly believe that the one true
  291. way to use Emacs is by using it the way it was intended to be used (as
  292. far as navigation is concerned at least). That's why I've disabled all
  293. movement commands with arrows (and keys like page up, page down, etc) - to prevent you from being tempted to
  294. use them.
  295. If you'd still like to use the arrow keys just invoke `M-x
  296. guru-mode` to enable them for the duration of your
  297. current Emacs session or add the following snippet to your
  298. personal Emacs customization to enable them permanently:
  299. ```lisp
  300. (setq prelude-guru nil)
  301. ```
  302. ### Windows compatibility
  303. While everything in Prelude should work fine in Windows, I test it only
  304. with Linux & OSX, so there are Windows related problems from time to
  305. time. This situation will probably improve over time.
  306. ## Share the knowledge
  307. [WikEmacs](http://wikemacs.org) collects useful resources for working
  308. with GNU Emacs. Please, take the time to peruse and improve them as
  309. you accumulate knowledge about Emacs. Prelude makes this especially
  310. easy, since it bundles
  311. [MediaWiki support](http://wikemacs.org/wiki/Mediawiki.el) + the
  312. settings required to access WikEmacs right away.
  313. ## Known issues
  314. Check out the project's
  315. [issue list](https://github.com/bbatsov/prelude/issues?sort=created&direction=desc&state=open)
  316. a list of unresolved issues. By the way - feel free to fix any of them
  317. and send me a pull request. :-)
  318. ## Support
  319. Support is available via the Prelude Google Group <emacs-prelude@googlegroups.com>.
  320. ## Contributors
  321. Here's a [list](https://github.com/bbatsov/prelude/contributors) of all the people who have contributed to the
  322. development of Emacs Prelude.
  323. ## Bugs & Improvements
  324. Bug reports and suggestions for improvements are always
  325. welcome. GitHub pull requests are even better! :-)
  326. Cheers,<br/>
  327. [Bozhidar](https://twitter.com/bbatsov)