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
After 63dc8f7ea0 `SPC '` started to ask
for "Run program" instead of opening the shell with the defined shell.
This commit remove the `call-interactively` that are causing this
problem. `SPC u SPC '` is still working as far as I tested.
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`
- move evil-org to org layer
- move org-plus-contrib to spacemacs-org layer
- remove toc-org from the list of package for org layer
- give ownership of the org package to org layer
- invent a package named default-org in spacemacs-org layer in order
to let the ownership of org package to org layer
- remove unnecessary :mode keyword in use-package from for org
This makes sure that all the setup happens at the same time. Previously
some setup happened at loading time of esh-mode while some happened in
eshell-mode-hook. Everything output between this (the first prompt)
looks different.
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.
Isolate the calls to bepo macro in pre-init or post-init functions, this
way they are called a the right time in the loading process.
Previously the calls were all in the config.el file which is loaded
before the package configuration phase.
New package :step 'bootstrap', this step happens before 'pre' packages.
A new layer names 'spacemacs-bootstrap' gather all the ':step bootstrap'
packages. This layer is special and is always the first element of
the variable 'configuration-layer--layers' which assure that all
bootstrap packages are configured first.
This new layer leverages the configuration layer system, removes the
clutter of package installations in the function 'spacemacs/init' and
isolate the bootstrap packages in one place.
The mac port build supports this out of the box, but the version
installed with `brew install emacs --with-cocoa` requires this variable
to be cleared.
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 https link-type opens the local copies of the Spacemacs documentation files with
the spacemacs/view-org-file function. It supports GitHub style heading links
For example, the link:
https://github.com/syl20bnr/spacemacs/blob/develop/layers/org/README.org#links
Will be handled similary to as if it was:
file:~/.emacs.d/layers/org/README.org::*links
Also the `space-doc' mode will be applied.
Refactored GH style anchor search.
`space-doc-mode` - Buffer local minor mode for Spacemacs documentation files. The mode hides org meta tags.
Enabled when viewing documentation via `SPC` `h` `SPC`
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
- add `l` to workspace transient state to go back to layout transient
state
- remove erroneous `l` and `h` keys on layouts transient state
- unique documentation toggle for layouts and workspaces
- reformat and sort transient states documentation
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.
Add layer variables `restclient-use-org` to use `ob-http` instead of
`resctlient`
Add support for easy addition of org-babel languages by appending to
`org-babel-load-languages` alist in org post-config use-package hook.
By convention, jump back should be on `b`, not `u`
Since `SPC j u` is free, move as well `SPC j U` to `SPC j u`.
`SPC j b` for bookmark jump is already available under `SPC f b`
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.
To follow with the refactor of the holy-mode which uses the
emacs state of evil mode, the hybrid mode now uses the evil hybrid
state.
We have now a clean symmetry between all the editing styles where each
of them has an associated state:
- vim = insert state
- emacs = emacs state
- hybrid = hybrid state
This gives consistent properties to all editing styles and most
importantly allows to have true isolation of key binding maps. It has
the huge benefit to be easier to explain since now everything can
leverage the evil API regarding key bindings.
Note: Regular Emacs key binding functions can still be used for emacs
and hybrid states so there is no regression with the previous
implementation, we just gain better isolation at the cost of a few
duplicated lines of code which will be easy to update as needed if
evil upstream code changes (this code has been commented with a link
to the upstream code).
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.
This keeps the keybinding specific to the visual-line minor mode, and
fixes#5418. Reverting the bindings on the :off toggle is no longer
necessary as well, turning off visual-line-mode will handle it.
`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
While seemingly equivalent, this binding change can cause brittle
behavior in at least one case (used in conjunction with
multiple-cursors). Such a highly niche customization would probably be
better in a personal config, unless a case can be made that all
spacemacs users would benefit.
Using window-numbering-assign is simpler and more reliable than using
window-numbering-before-hook and neo-after-create-hook.
Duplicates older commit 2ff22934e7 which
somehow didn't survive the splitting of spacemacs layer into smaller
spacemacs-* layers.
- Replace `M-SPC` and `S-M-SPC` by the more conventional `SPC m .`
- Reorganize the code in packages.el
- Add image in README and list bindings with explicit `SPC m` prefix
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.
This reverts commit decd5235a9.
The smooth-scrolling package is not required when
dotspacemacs-smooth-scrolling is nil so it is not possible to use a
function of this package to disable it.
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.
16cb4f2 changed the default binding for RET to org-agenda-goto, this
changes it back to the default behavior of org-agenda-switch-to
making it consistent with the transient state and org documentation.
This was asked for in the gitter chat. I thought at first it would be
great for when people wanted to open many perspectives at the same time,
but now I don't think the same. It'd be very hard to modify the macro
for adding custom layouts to make this argument optional, so I leave it
at @syl20bnr discretion.
1. The register name should be a character not a symbol.
2. Combine toggle-maximize-centered-buffer and bzg-big-fringe-mode to
make new minor mode that combines the two effects.
3. Fix problem where the mode could only be enabled if there was more
than one window, which makes no sense.
4. Use window-configuration-to-register function
