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.

408 lines
14 KiB

14 years ago
14 years ago
  1. Emacs Prelude
  2. =============
  3. Emacs is probably the best text editor in the world. However, the
  4. process of coming up with a useful Emacs configuration is long and
  5. difficult. It's this process that separates you from truly taking
  6. advantage of Emacs's power. I like to refer to this process as the
  7. **Prelude**. **Emacs Prelude** has the goal to ease the initial Emacs
  8. setup process and to provide you with a much more powerful and
  9. productive experience than the one you get out of the box. By using
  10. **Emacs Prelude** you're basically getting a *"Get me out of the
  11. Prelude, I just want to use Emacs"* card.
  12. Emacs Prelude is compatible **ONLY with GNU Emacs 24.x**.
  13. ## Fast Forward
  14. Assuming you're using an Unix-like OS (`*BSD`, `GNU/Linux`, `OS X`, `Solaris`,
  15. etc), you already have Emacs 24 installed, as well as `git` & `curl` you
  16. can skip the whole manual and just type in your favorite shell the
  17. following command:
  18. ```bash
  19. $ curl -L https://github.com/bbatsov/prelude/raw/master/utils/installer.sh | sh
  20. ```
  21. You can now power up your Emacs, sit back and enjoy Prelude,
  22. forgetting about the rest of this manual.
  23. There are two environment variables you can use to control the
  24. source repository and the installation directory. To change the
  25. installation directory:
  26. ```bash
  27. $ export PRELUDE_INSTALL_DIR="$HOME/.emacs.d" && curl -L https://github.com/bbatsov/prelude/raw/master/utils/installer.sh | sh
  28. ```
  29. To change the source repository:
  30. ```bash
  31. $ export PRELUDE_URL="https://github.com/yourname/prelude.git" && curl -L https://github.com/bbatsov/prelude/raw/master/utils/installer.sh | sh
  32. ```
  33. Note that the installer will back up any existing `.emacs` file or
  34. `.emacs.d` since it will unpack Prelude's code in `.emacs.d`. If
  35. you're doing a manual install make sure you don't have a `.emacs` file
  36. or back up your existing `.emacs.d` directory manually.
  37. Don't forget to adjust your `prelude-modules.el` file once the installation is done.
  38. By default most of the modules that ship with Prelude are not loaded.
  39. ## Installing Emacs 24
  40. Obviously to use the Emacs Prelude you have to install Emacs 24
  41. first. Have a look at the [WikEmacs articles on installing Emacs](http://wikemacs.org/wiki/Installing_Emacs).
  42. ## Installation
  43. ### Automated
  44. You can install **Emacs Prelude** via the command line with either `curl` or
  45. `wget`. Naturally `git` is also required.
  46. #### Via Curl
  47. If you're using `curl` type the following command:
  48. ```bash
  49. $ curl -L https://github.com/bbatsov/prelude/raw/master/utils/installer.sh | sh
  50. ```
  51. #### Via Wget
  52. If you're using `wget` type:
  53. ```bash
  54. $ wget --no-check-certificate https://github.com/bbatsov/prelude/raw/master/utils/installer.sh -O - | sh
  55. ```
  56. ### Manual
  57. ```bash
  58. $ git clone git://github.com/bbatsov/prelude.git path/to/local/repo
  59. $ ln -s path/to/local/repo ~/.emacs.d
  60. $ cd ~/.emacs.d
  61. ```
  62. You'd do well to replace `~/.emacs.d` with the value of
  63. `user-emacs-directory` for your OS. You can check the value by doing
  64. `C-h v user-emacs-directory` inside Emacs.
  65. ## Updating Prelude
  66. The update procedure is fairly straightforward:
  67. ```bash
  68. $ cd path/to/prelude/installation
  69. $ git pull
  70. ```
  71. The `path/to/prelude/installation` is usually `~/.emacs.d` (at least
  72. on Unix systems).
  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 installation is done.
  104. ## Running
  105. Nothing fancy here. Just start Emacs as usual. Personally I run Emacs
  106. in daemon mode:
  107. ```bash
  108. $ emacs --daemon
  109. ```
  110. Afterwards I connect to the server with either a terminal or a GUI
  111. client like this:
  112. ```bash
  113. $ emacsclient -t
  114. $ emacsclient -c
  115. ```
  116. You'd probably do well to put a few aliases in your `.zshrc` (or
  117. `.bashrc`):
  118. ```bash
  119. alias e=emacsclient -t
  120. alias ec=emacsclient -c
  121. alias vim=emacsclient -t
  122. alias vi=emacsclient -t
  123. ```
  124. The last two aliases are helpful if you're used to editing files from
  125. the command line using `vi(m)`.
  126. ## Getting to know Prelude
  127. Certainly the best way to understand how Prelude enhances the default
  128. Emacs experience is to peruse Prelude's source code (which is
  129. obviously written in Emacs Lisp). Understanding the code is not
  130. necessary of course. Prelude includes a `prelude-mode` minor Emacs mode
  131. which collects some of the additional functionality added by
  132. Prelude. It also adds an additional keymap that binds many of those
  133. extensions to keybindings.
  134. ### Keymap
  135. #### Global
  136. Keybinding | Description
  137. -------------------|------------------------------------------------------------
  138. <kbd>C-M-h</kbd> | Kill the previous word(`backward-kill-word`). (as in Bash/Zsh)
  139. <kbd>C-x \</kbd> | `align-regexp`
  140. <kbd>C-+</kbd> | Increase font size(`text-scale-increase`).
  141. <kbd>C--</kbd> | Decrease font size(`text-scale-decrease`).
  142. <kbd>C-x O</kbd> | Go back to previous window (the inverse of `other-window` (`C-x o`)).
  143. <kbd>C-x ^</kbd> | Join two lines into one(`join-line`).
  144. <kbd>C-x p</kbd> | Start `proced` (manage processes form Emacs, works only in Linux).
  145. <kbd>C-x m</kbd> | Start `eshell`.
  146. <kbd>C-x M-m</kbd> | Start your default shell.
  147. <kbd>C-x C-m</kbd> | Alias for `M-x`.
  148. <kbd>C-h A</kbd> | Run `apropos` (search in all Emacs symbols).
  149. <kbd>M-\</kbd> | Run `hippie-expand` (a replacement for the default `dabbrev-expand`).
  150. <kbd>C-x C-b</kbd> | Open `ibuffer` (a replacement for the default `buffer-list`).
  151. <kbd>F12</kbd> | Toggle the Emacs menu bar.
  152. <kbd>C-x g</kbd> | Open Magit's status buffer.
  153. <kbd>C-=</kbd> | Run `expand-region` (incremental text selection).
  154. #### Prelude Mode
  155. Keybinding | Description
  156. -------------------|------------------------------------------------------------
  157. <kbd>C-c o</kbd> | Open the currently visited file with an external program.
  158. <kbd>C-c g</kbd> | Search in Google for the thing under point (or an interactive query).
  159. <kbd>S-RET</kbd> | Insert an empty line and indent it properly (as in most IDEs).
  160. <kbd>C-S-up</kbd> | Move the current line up.
  161. <kbd>C-S-down</kbd> | Move the current line down.
  162. <kbd>C-c n</kbd> | Fix indentation in buffer and strip whitespace.
  163. <kbd>C-c f</kbd> | Open recently visitted file.
  164. <kbd>C-M-\</kbd> | Indent region (if selected) or the entire buffer.
  165. <kbd>C-c u</kbd> | Open URL in your default browser.
  166. <kbd>C-c e</kbd> | Eval a bit of Emacs Lisp code and replace it with its result.
  167. <kbd>C-c s</kbd> | Swap two active windows.
  168. <kbd>C-c d</kbd> | Duplicate the current line (or region).
  169. <kbd>C-c r</kbd> | Rename the currently visited file and buffer.
  170. <kbd>C-c t</kbd> | Open a terminal emulator (`ansi-term`).
  171. <kbd>C-c k</kbd> | Kill all open buffers except the one you're currently in.
  172. <kbd>C-c h</kbd> | Open Helm (a useful means of navigating your buffers and project files).
  173. #### Projectile
  174. Here's a list of functionality provided by [Projectile](https://github.com/bbatsov/prelude):
  175. Keybinding | Description
  176. -------------------|------------------------------------------------------------
  177. <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.
  178. <kbd>C-c p T</kbd> | Display a list of all test files(specs, features, etc) in the project.
  179. <kbd>C-c p g</kbd> | Run grep on the files in the project.
  180. <kbd>C-c p b</kbd> | Display a list of all project buffers currently open.
  181. <kbd>C-c p o</kbd> | Runs `multi-occur` on all project buffers currently open.
  182. <kbd>C-c p r</kbd> | Runs interactive query-replace on all files in the projects.
  183. <kbd>C-c p i</kbd> | Invalidates the project cache (if existing).
  184. <kbd>C-c p R</kbd> | Regenerates the projects `TAGS` file.
  185. <kbd>C-c p k</kbd> | Kills all project buffers.
  186. <kbd>C-c p d</kbd> | Opens the root of the project in `dired`.
  187. <kbd>C-c p e</kbd> | Shows a list of recently visited project files.
  188. <kbd>C-c p a</kbd> | Runs `ack` on the project. Requires the presence of `ack-and-a-half`.
  189. <kbd>C-c p l</kbd> | Runs a standard compilation command for your type of project.
  190. <kbd>C-c p p</kbd> | Runs a standard test command for your type of project.
  191. <kbd>C-c p z</kbd> | Adds the currently visited to the cache.
  192. <kbd>C-c p s</kbd> | Display a list of known projects you can switch to.
  193. If you ever forget any of Projectile's keybindings just do a:
  194. <kbd>C-c p C-h</kbd>
  195. ### Automatic package installation
  196. The default Prelude installation comes with a bare minimum of
  197. functionality. It will however install add-ons for various programming
  198. languages and frameworks on demand. For instance - if you try to open
  199. a `.clj` file `clojure-mode`, `nrepl.el` and prelude's enhanced Lisp
  200. configuration will be installed automatically for you.
  201. You can, of course, install anything you wish manually as well.
  202. ### Color Themes
  203. Emacs 24 ships with a new theming facility that effectively renders
  204. the old color-theme package obsolete. Emacs 24 provides a dozen of
  205. built-in themes you can use out-of-the-box by invoking the `M-x
  206. load-theme` command.
  207. [Zenburn](https://github.com/bbatsov/zenburn-emacs) is the default color theme in Prelude, but you can change it
  208. at your discretion. Why Zenburn? I (and lots of hackers around the
  209. world) find it pretty neat for some reason. Personally I find the
  210. default theme pretty tiresome for the eyes, that's why I took that
  211. "controversial" decision to replace it. You can, of course, easily go
  212. back to the default (or select another theme entirely).
  213. To disable Zenburn just put in your personal config the following
  214. line:
  215. ```lisp
  216. (disable-theme 'zenburn)
  217. ```
  218. Or you can use another theme altogether by adding something like:
  219. ```lisp
  220. (load-theme 'solarized-dark t)
  221. ```
  222. P.S. Solarized is not available by default - you'll have to install it from MELPA first.
  223. ### Personalizing
  224. Fork the official Prelude repo and add your own touch to it. You're advised to avoid changing stuff outside of the
  225. personal folder to avoid having to deal with git merge conflicts in the future.
  226. If you'd like to add some auto installation of packages in your
  227. personal config use the following code:
  228. ```lisp
  229. (prelude-ensure-module-deps '(some-package some-other-package))
  230. ```
  231. #### Disabling whitespace-mode
  232. Although `whitespace-mode` is awesome some people might find it too
  233. intrusive. You can disable it in your
  234. personal config with the following bit of code:
  235. ```lisp
  236. (setq prelude-whitespace nil)
  237. ```
  238. #### Disable flyspell-mode
  239. If you're not fond of spellchecking on the fly:
  240. ```lisp
  241. (setq prelude-flyspell nil)
  242. ```
  243. ## Caveats & Pitfalls
  244. ### Problems with flyspell-mode
  245. Prelude makes heavy use of the flyspell-mode package for spell
  246. checking of various things. The proper operation of flyspell depends
  247. on the presence of the `aspell` program and an `en` dictionary on your
  248. system. You can install `aspell` and the dictionary on OS X with
  249. `homebrew` like this:
  250. ```bash
  251. $ brew install aspell --with-lang=en
  252. ```
  253. On Linux distros - just use your distro's package manager.
  254. ### Ugly colors in the terminal Emacs version
  255. If your Emacs looks considerably uglier in a terminal (compared to the
  256. GUI version) try adding this to your `.bashrc` or `.zshrc`:
  257. ```bash
  258. $ export TERM=xterm-256color
  259. ```
  260. Source the `.bashrc` file and start Emacs again.
  261. ### MELPA error on initial startup
  262. If you get some http connection error related to the MELPA repo
  263. just do a manual `M-x package-refresh-contents` and restart Emacs
  264. afterwards.
  265. ### No arrow navigation in editor buffers
  266. This is not a bug - it's a feature! I firmly believe that the one true
  267. way to use Emacs is by using it the way it was intended to be used (as
  268. far as navigation is concerned at least). That's why I've disabled all
  269. movement commands with arrows (and keys like page up, page down, etc) - to prevent you from being tempted to
  270. use them.
  271. If you'd still like to use the arrow keys just invoke `M-x
  272. guru-mode` to enable them for the duration of your
  273. current Emacs session or add the following snippet to your
  274. personal Emacs customization to enable them permanently:
  275. ```lisp
  276. (setq prelude-guru nil)
  277. ```
  278. ### Windows compatibility
  279. While everything in Prelude should work fine in Windows, I test it only
  280. with Linux & OSX, so there are Windows related problems from time to
  281. time. This situation will probably improve over time.
  282. ## Share the knowledge
  283. [WikEmacs](http://wikemacs.org) collects useful resources for working
  284. with GNU Emacs. Please, take the time to peruse and improve them as
  285. you accumulate knowledge about Emacs. Prelude makes this especially
  286. easy, since it bundles
  287. [MediaWiki support](http://wikemacs.org/wiki/Mediawiki.el) + the
  288. settings required to access WikEmacs right away.
  289. ## Known issues
  290. Check out the project's
  291. [issue list](https://github.com/bbatsov/prelude/issues?sort=created&direction=desc&state=open)
  292. a list of unresolved issues. By the way - feel free to fix any of them
  293. and send me a pull request. :-)
  294. ## Support
  295. Support is available via the Prelude Google Group <emacs-prelude@googlegroups.com>.
  296. ## Contributors
  297. Here's a [list](https://github.com/bbatsov/prelude/contributors) of all the people who have contributed to the
  298. development of Emacs Prelude.
  299. ## Bugs & Improvements
  300. Bug reports and suggestions for improvements are always
  301. welcome. GitHub pull requests are even better! :-)
  302. Cheers,<br/>
  303. [Bozhidar](https://twitter.com/bbatsov)