Since Helm is another option to Ido, users who want to use it fully
should benefit from the default Prelude setup. If some users don't like,
they can always disable global Helm mode according to the instructions
in the homepage. User can enable Helm everywhere with
prelude-helm-everywhere.
This change also enables Helm version of command history in shell and
eshell. It also adds minibuffer history without overrides any key
binding in minibuffer-local-map.
Since some users prefer using default Prelude commands, a new global
mode is defined: prelude-global-helm-mode. When activate, Helm binds
some global key bindings to its own commands. When deactivate, Helm
removes the bindings and Prelude uses the default bindings.
The current prelude-helm only uses a single command of Helm, which
is a waste given how Helm contains many other commands. When
prelude-helm is activated, users should be able to utilize all of these
useful commands. If a user wants to use Helm, he will want to use all of
its features anyway.
prelude-helm is configured that it is able to be used with this [guide](http://tuhdo.github.io/helm-intro.html).
If you hit esc-key in terminal mode very quickly, it gets interpreted
as meta-key, which makes evil-mode unusable in terminal mode. The
default value of 0.01 doesn't completely fix this behavior, but
setting it to 0 does. The meta key still works fine with it at 0.
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`
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.
