By convention, code markup (`~`) is reserved for keybindings in Org-based
documentation in Spacemacs. Verbatim markup (`=`) is reserved for code and
other code-like things. So change several readmes to reflect this convention.
Use verbatim markup for things like (non-exhaustive list):
- Emacs Lisp functions, modes, buffers, etc.
- Environment variables
- Directory paths
- Code in general
spacemacs/add-flycheck-hook was not really hooking anything, change the name
to better reflect what it does.
Also changed the push for a add-to-list to avoid duplicates.
Enabling a company backend for a specific mode was a tedious tasks with code
scattered at different locations, one for local variable definitions, one for
company hook function definitions and another where the backends were pushed to
the local variables (which was problematic, since we ended up pushing the same
backends over and over again with `SPC f e R`, pushes have been replaced by
add-to-list calls in the new macro).
All these steps are now put together at one place with the new macro
spacemacs|add-company-backends, check its docstring for more info on its
arguments.
This macro also allows to define arbitrary buffer local variables to tune
company for specific modes (similar to layer variables via a keyword :variables)
The code related to company backends management has been moved to the
auto-completion layer in the funcs.el file. A nice side effect of this move is
that it enforces correct encapsulation of company backends related code. We can
now easily detect if there is some configuration leakage when the
auto-completion layer is not used. But we loose macro expansion at file loading
time (not sue it is a big concern though).
The function spacemacs|enable-auto-complete was never used so it has been
deleted which led to the deletion of the now empty file core-auto-completion.el.
The example in LAYERS.org regarding auto-completion is now out of date and has
been deleted. An example to setup auto-completion is provided in the README.org
file of the auto-completion layer.
As per #6233 add support for `intero-apply-suggestions` behind `SPC m r s`,
and move the prefix declaration for "haskell/refactor" to the other prefix declarations,
since it is no longer only relevant for hlint.
- Add option to disable by default
- Use local-vars hook to allow per-project enable/disable
- Don’t enable helm-gtags-mode (no need)
- Move emacs bindings from helm-gtags-mode-map to ggtags-mode-map
This commit defines:
- spacemacs-default-jump-handlers: a list of functions that can jump to
definition in ALL modes.
- spacemacs-jump-handlers-MODE: a list of functions that can jump to
definition in MODE.
- spacemacs-jump-handlers: a buffer-local list of functions that can
jump to definition. This is made up of the values of the two previous
variables whenever a given major mode is activated.
- spacemacs/jump-to-definition: a function that tries each function in
spacemacs-jump-handlers in order, and stops when one of them takes us
somewhere new.
- spacemacs|define-jump-handlers: a macro that
* defines spacemacs-jump-handlers-MODE, possibly filled with initial
functions
* defines a function that is added to the hook of the given MODE
* binds “SPC m g g” of that MODE to spacemacs/jump-to-definition
This is an attempt to harmonize all the different approaches to jumping.
Specifically,
- Existing intelligent jump packages that work for only a single mode
should go to the beginning of spacemacs-jump-handlers-MODE. E.g.
anaconda for python, ensime for scala, etc.
- Packages like gtags that work for several modes (but potentially not
all) and which is dumber than the intelligent jumpers should go the
the END of spacemacs-jump-handlers-MODE.
- Packages like dumb-jump that work for all modes should go to
spacemacs-default-jump-handlers.
In all cases the order of the jump handlers in each list should be from
most to least intelligent.
Fixes#6619
It is better to directly hook function using the conventional hook
functions.
Replace usage of (concat ...) by a (format ...) from which is more
readable.
- add haskell-completion-backend variable that should be used to select
desired completion backend
- add support for intero (based on @cydparser layer)
- remove ghci-ng support
- update readme file:
- document haskell-completion-backend variable
- remove installation notes for ghc-mod as they are not relevant
anymore
- remove ghci-ng section
- overall readme file fixes and improvements
This is a very opinionated option and works very poorly on even
moderately large projects as it invokes `hasktags` synchronously,
freezing the editor for several seconds on every save. Users who want
this behavior should enable it manually.
Fixes#6292.
You don't need ghc-mod to do code completion with ghc 7.10+. GHCI has built-in code-completion suggestions you can aske for. This is what company-ghci does.
This make `SPC h SPC` as default binding for accessing `helm-spacemacs`,
by either A) changing all the documentation; and B) adding a deprecation
message for `SPC f e h`.
The deprecation use a warning, because if a message is used it's hidden
directly when the helm buffer is shown, making it nearly unnoticeable
for the user.
When user disabled ghc-mod, haskell mode should fallback to interactive
mode, so type bindings (and some others) are working properly. It's also
useful for ghci-ng users, but doesn't affect ghci-ng-only bindings.
Fix#3777
By default `C-c C-l` shows following error:
```
haskell-mode-enable-process-minor-mode: Run ‘C-h f haskell-mode‘ for instruction how to setup a Haskell interaction mode.
```
Which might confuse users and they might end up setting
interactive-haskell-mode, which in most cases not what we want.
Also, it gives short key binding for emacs-only editing style users to
bring up REPL.
- fix some inaccuracies
- add more notes about using ghc-mod
- add more notes about using ghci-ng
- add more notes about using shm
- add more troubleshooting
- update section about setting up PATH by updating value of
=exec-path= (previously it was saying to update it in =user-init=
function, but looks like you need to do it in =user-config=) -
following #1718
- add FAQ section
- add note about setting up =stack-ghci= as =haskell-process= (as
noted in #2142)
- add note about fixing problems with =ghc-mod= and =stack=
- add note about fixing stuck REPL (following #3271)
