I often work on Go projects under a symlink, e.g. ~/Code/project points to
$GOPATH/src/github.com/grncdr/...
This works fine 99% of the time, but gorename doesn't follow symlinks in order
to get the "truename" of a file, so it will complain about
~/Code/project/somefile.go not belonging to any package. This fixes that
situation by ensuring that gorename is only passed the true filename.
Add `company-dcd` package that uses DCD (a completion daemon for D) to
provide better IDE features:
- Better code completion.
- Jump to definition.
- Search symbol references.
- Apply `/` and `//` rules (double / is for private functions)
- Add missing `spacemacs/` prefixes
- Move functions used outside of spacemacs-base layer to
core/core-funcs.el
- Remove unused functions
Commit originally intented to only rename linum-update-window-scale-fix
to spacemacs/linum-update-window-scale-fix :-)
Jade has been deprecated and there is little need to support jade to
support jade anymore. If people need jade-mode, they can install the
package themselves and configure it. Pug is the renamed Jade project.
Hook semantic is to be used with run-hooks API and run all hooks
sequentially, jump list semantic is different since the running
functions are not guaranteed to be executed so we prefer using regular
list API to manage jump-lists.
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.
Also removed redundant `mode` entries and instead added ones that are
missing in original package. Updated README to represent this change and
fixed typo in installation message about the layer name.
SPC j F and SPC j V don't fit the SPC j prefix because they require
the thing under point to be an Emacs lisp thing, which means that these
bindings should be major mode specific.
To replace them and accordingly to the convention the key bindings
SPC m g G in Emacs Lisp buffers has been added to go to definition
in other window.
SPC j f and SPC j v (minus letters) don't require the current buffer
to be Emacs Lisp and thus I only updated the documentation about them
mentioning that they're about Emacs Lisp variables and functions.
- 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
The member function works slightly different on the master branch of
emacs than in emacs 24.5 or emacs 25 release candidates. This might be a
bug in emacs but for now we can add a check if python-test-runner is a
list to work around that.
Fix#6246.
I think MELPA has an `old-names` back
[compatibility](https://github.com/melpa/melpa/issues/4159) measure for
cases like this, but for now it isn't working. And it's breaking all new
installs that use the java layer.
IPython 5 does no longer use readline and so the emacs integration is
broken. See also
http://ipython.readthedocs.io/en/stable/whatsnew/version5.html#id1Fix#6622 and related to #6580
This also works if different environments have different IPython
versions since the shell parameters are setup on every environment
switch.
These changes will allow users to evaluate hy code in a repl using an
inferior-lisp process. It requires that users have hy installed via pip
in their local python enviornment.
Add smartparens-mode and documentation
I moved the add-hook for smartparens call to
python/post-init-smartparens. Keybindings were also updated to match
the ones for the Inferior REPL process for Python. Also added some
documentation for required hy pacakge, and the keybindings to
README.org.
When Spacemacs is used in daemon mode, the `PATH` is not always filled
up with user-defined run paths when Spacemacs load the packages. The
`toggle` of the `vmd` package is checking for the `vmd` executable which
may be in one of the user path, what prevent the package to be loaded,
even if the executable is available at execution time.
If people want to use `vmd`, setting `markdown-live-preview-engine`
should be enough, there is no need for checking for the executable to be
present, this is the responsability of the user to ensure this.
If only ipython is installed, command $ ipython notebook fails with ImportError: No module named 'notebook'. Correct to specify dependency to include the notebook server.
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
Helm-flx, which is included as a core package, requires a minimum Emacs
version of 24.4. As it stands attempting to install Spacemacs on Emacs
24.3 or below will break on helm-flx.
Or `,.` with the shortcut, this is a more standard approach.
Use the :evil-leader-for-mode keyword to bind the transient state
Add space in the :doc of the transient state because auto-indent of
elisp code is broken otherwise.
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.
According to the conversation in [0] ':' is removed from
electric-indent-chars in python-mode because typing ':' in
> for i in range(10):
> print(i)
> for i in range(10)_
with the point at _ indents the third line. This is not happening in
Emacs 24.5 anymore.
[0] aed0fc8ef8
- Prefer add-to-list function to alter golden-ratio variables so the lists
are less likely to grows as users reload their spacemacs config.
- Move some config to layers when appropriate
- Sort alphabetically the values
- Remove some duplicates in exclude-modes
This commit adds the 'inf-ruby-auto-enter method to
'compilation-filter-hook, automatically entering inf-ruby-mode when it
hits a breakpoint (see the
[inf-ruby-manual](https://github.com/nonsequitur/inf-ruby/#manual) for
more details).
The hook is added locally to the rspec-compilation-mode-hook to avoid
global slowdown, as the compilation-filter-hook is called whenever a
new line is entered.
specific directory.
This commit creates a 'ruby/rspec-verify-directory command, which
prompts for a directory and runs rspec on it. This command is bound to
ruby-modes' keymaps under the "td" keybinding.
(In vim style) this leaves the `n` to its usual binding to repeat the
last search which is much more practical when searching for package to
install.
elm-package-next / elm-packge-previous don't seem to do much more than
move to next/previous line so not much functionality is lost.
This allows python-test-runner to also be a list of either '(nose
pytest) or '(pytest nose) which then calls the correct test runner in
the dispatch functions.
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.
`spacemacs` now handles `rainbow-delimiters-mode` by adding it to the
`prog-mode-hook`, if wanted by the user. Some layers are adding it on
their own mode-hook, having for effect that `rainbow-delimiters-mode` is
called twice, which disable it.
This commit remove these layer-specific definitions of
`rainbow-delimiters` as it is now handled by the `spacemacs`
distribution. It also takes care of running `prog-mode-hook` in modes
that are not derived from it.
Fixes#3902
It's not possible to get full backtraces in these instances when an
error is signaled, and I think we should generate full backtraces when
debug-on-error is enabled as a general rule.
I had to make this change at one place to track down the root of problem
2 in #5200.
Felt more comfortable running this over https. Not sure what the risks
are of piping files into a root privilege tar process, but the server
supports it so may as well use it.
