With this, after we create a special buffer, the major-mode get set
automatically. For example, we create a new buffer named "ruby.rb",
`ruby-mode` was automatically enabled.
In `prelude-common-lisp.el`, look in both `~/quicklisp/` and
`~/.quicklisp/` for `slime-helper.el`, on the assumption that most users
will have Quicklisp installed in one of these two locations.
This commit fixes#582
There are two reasons for doing this:
- It's inefficient, we don't have to define the pairs every time we
enter the mode.
- It's extremely difficult to override the pair definition, even with
`eval-after-load` and `add-hook`
- Rename and move yank indent vars into prelude-custom.el
- Add coffee-mode to prelude-indent-sensitive-modes
- Do not mess up indentation when cleanup with indentation sensitive
modes, such as Python.
- Create a macro `with-region-or-buffer` to replace the prelude wrapper
around `untabify` and `indent-region`
- Remove the function operated on buffers, cause we only need the dwim
one
I don't know if CSS should be count as a programming language, but the
utilities provided in the `prelude-prog-mode-hook`, such as
smartparens, whitespace-mode, comment annotation, are also very useful
when editing CSS files.
web-mode's auto paring is in conflict with smartparens. With
smartparens, since the closing '>' is inserted right after the opening
'<' and web-mode is not aware of that, the extra closing '>' would be
inserted. That's very annoying.
- Code indent offset is subjected to personal taste, I think we should
stick to the web-mode default, which is sensible enough, and leave it
to the user to decide.
- `web-mode-disable-autocompletion` is no longer used by web-mode.
- As to `newline-and-indent`, I think we should be consistent across all
major modes. And this line of code will become useless with Emacs 24.4.
At least on my Windows 7 machine, `user-emacs-directory` prints `~/.emacs.d`, which is not really useful, since you also then have to realize that the tilde refers to the roaming appdata directory. I think this way of documenting would perhaps be more immediately useful. For probably almost all other platforms the tilde path will work just fine.
* Colour handling in zsh (& don't use "colors" as funcname)
* Quote-protect -z test
* Clean up verbose var-printout
* git clone requires empty dir - tweak script to make it work with
an existing dir
* Unquote asterisks for shell-expansion when byte-compiling
