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.
clojure-defun-style-default-indent has been deprecated in favor of
clojure-indent-style. This is no longer a toggle but one of three
keywords. As it affects the way code is indented, and you should not
need to change your indentation style multiple times while editing, it
should not be a toggle. It's simple enough for the user to setq it to
desired value.
If desired, it may be added back as a completing-read selection (but I
don't think it's necessary).
Error was caused by unnecessarily wrapping cider test fns in
spacemacs//cider-eval-in-repl-no-focus. Test fns do not move focus to
repl anyways, and it caused a wrong-type-argument error.
The added bindings are to more closely match cider bindings (under C-c
C-t). Now spacemacs cider test fns mirror the cider ones.
Hybrid means vim-like in normal and emacs-like in insert. This is a
normal-state compatibility tweak (has no effect on insert-state
bindings), so it belongs.
When trying to run a single test function with LEADER m t t in a Golang
test file, spacemacs failed to find functions which had underscores in
their names. This commit simply adds an underscore to the regular
expression which spacemacs uses when searching for the current test
function.
Move all semantic related config to semantic post-init and correctly
fix the error with void function semantic-idle-summary-mode when
opening a python without the semantic layer enabled.
Squashing the 3 commits of #5688:
Commit 1
--------
Add prefix doc in idris layer
Also remove `idris-ensure-process-and-repl-buffer` as this is not an
interactive command
Add `SPC m l` keybinding for extracting lemma
Bind `SPC m c` to `idris-case-dwim`
Commit 2
--------
Fix registering idris repl
Commit 3
--------
Add basic auto-completion for idris mode
Fix#4292
If tern binary isn't found, warn the user of missing binary and do not
enable tern package(else it makes emacs unresponsive).
Allow user to disable missing binary warning via configuration layer
variable `javascript-disable-tern-missing-warning`
Update documentation by removing obsolete keybindings that
were deleted from +lang/markdown layer in 7b6678e.
In particular the ~SPC m =~, ~SPC m -~ and ~SPC m l [h/j/k/l]~
have been superseded by the **Movement** bindings.
a new variable, scala-auto-start-ensime, determines if ensime starts
when a scala file is loaded.
make scala-auto-start-ensime default to t
The current behaviour is to autostart so this will preserve it.
Adding documentation for scala-auto-start-ensime
removed a space
make scala-auto-start-ensime default to t
The current behaviour is to autostart so this will preserve it.
Adding documentation for scala-auto-start-ensime
removed a space
The previous installation instructions suggested that you install lein
via your OS package manager, but since the minimum required version to
run the plugins is 2.5.2 and some OS package managers are still
packaging versions in 1.x, linking to the official install instructions
is better.
Fixes#5612
Now Spacemacs will ask for layer installation when opening a file with
a known file type.
The auto-mode-alist entries are added by the file auto-layer.el in
the layers directory.
Easy insert of forms for lazy initialization can be done with the
interactive function configuration-layer//insert-lazy-install-form.
Change default value of dotspacemacs-enable-lazy-installation to t.
Change the key bindings:
- Remove SPC m p
- Better support for double leader keys for preview (,, and M-m M-m)
- Graph indentation on SPC m =
Add support for smartparens when it is used for {} pair.
Update the doc.
My first spacemacs layer, total elisp newb.
Does what it says in the README, with one bug:
I have auto-completion-enable-snippets-in-popup t in my .spacemacs
In faust files, only yas-keys that have a similar word in an open buffer
show up in the company menu.
Example: with no open buffers ne doesn't show a company menu,
if a file has the word nent in it, I get a menu with ne -> nentry (the snippet) and nent.
having ne$AnyTwoCharacters in the file also works, but just ne or nen doesn't.
Motivation
While disabling Evil in holy-mode makes its implementation shorter and
sounds elegant on the paper, in practice it puts a big burden on the
configuration parts which need to know if Evil is enable or not. This is
a bad separation of concerns and the bunch of fixes that we were forced
to do in the past weeks shows this issue. Those fixes were about
removing the knowledge of the activation of Evil by implementing new
dispatching functions to be used by layers, this is cumbersome and makes
Spacemacs layer configuration more subtle which is not good. There was
additional bad consequences of the removal of Evil state like the
impossibility to use Evil lisp state or iedit states, or we would have
been forced to implement a temporary activation of Evil which is
awkward.
Instead I reintroduce Evil as the central piece of Spacemacs design thus
Evil is now re-enabled in holy-mode. It provides the abstraction we need
to isolate editing styles and be able to grow the Spacemacs
configuration coverage sanely. Layers don't need to check whether the
holy mode is active or not and they don't need to know if Evil is
available (it is always available). We also don't need to write
additional dispatching functions, this is the job of Evil, and I think
it provides everything for this. Ideally configuration layer should be
implemented with only Evil in mind and the holy-mode (and hybrid-mode)
should magically make it work for Emacs style users, for instance we can
freely use `evil-insert-state` anywhere in the code without any guard.
Evil is now even more part of Spacemacs, we can really say that
Spacemacs is Emacs+Evil which is now an indivisible pair. Spacemacs
needed this stable API to continue on the right track.
While these changes should be rather transparent to the user, I'm sorry
for this experimental period, I failed to see all the implications of
such a change, I was just excited about the possibility to make Evil
optional. The reality is that Spacemacs has to embrace it and keep its
strong position on being Emacs+Evil at the core.
Implementation
- insert, motion and normal states are forced to emacs state using an
advice on `evil-insert-state`, `evil-motion-state` and
`evil-normal-state` respectively. These functions can be used freely in
the layer configuration.
- A new general hook `spacemacs-editing-style-hook` allow to hook any
code that need to be configured based on the editing style. Functions
hooked to this hook takes the current style as parameter, this
basically generalize the hook used to setup hjkl navigation bindings.
- ESC has been removed from the emacs state map.
- Revert unneeded changes
- Revert "evil: enter insert-state only from normal-state"
commit bdd702dfbe.
- Revert "avoid being evil in deft with emacs editing style"
commit f3a16f49ed.
Additional changes
All editing style packages have been moved to a layer called
`spacemacs-editing-styles`
Notes
I did not have time to attack hybrid mode, I should be able to do it
later.
