magit-log-all has the same with the old magit-log: show the commit log
immediately without asking for revision. We should use magit-git-log for
smoother transition to magit 2.1.
Calling `magit-blame-mode` directly is not advised as of Magit 2.1.0,
and will leave a buffer in read-only mode upon exit. `magit-blame` also
allows recursive blame upon repeated usage.
Rename the layer to idris-lang because idris-packages variable is used
by the package
Update key bindings to better fit spacemacs conventions
Convert markdown README to org
This removes idris-mode from the extra-langs layer and moves it to its
own layer with custom evil-leader keybindings. It also removes
documentation in extra-langs on other removed languages.
There are two major complications with idris-mode: it defines its own
evil-leader bindings which overwrite Spacemacs defaults, and it uses
the variable idris-packages, which Spacemacs uses to include the
idris-mode package, to define Idris packages to load for the current
buffer.
- Use compile instead of shell for cargo. This allow Emacs to parse the
output, including all the errors :)
- Added support for Racer (it works for me at least... hopefully for
others too)
Signed-off-by: JP-Ellis <coujellis@gmail.com>
This commit drastically simplify the previous commit by removing
the layer variable syntax-checking-check-on-buffer-change and
the associated usage of it.
This effectively make spacemacs use the default flycheck setting.
If the user wants to customize this behavior then she can modify
directly the flycheck variable.
Add a variable `syntax-checking-check-on-buffer-change` to the
`syntax-checking` layer which conditionally sets the variable
`flycheck-check-syntax-automatically` to:
- `'(save mode-enabled)` when nil
- `'(save idle-change new-line mode-enabled)` (the package default)
when non-nil
The various settings determine when Flycheck evaluates the buffer:
- `save` triggers a buffer check after buffer save.
- `mode-enabled` triggers a buffer check when `flycheck-mode` is
enabled.
- `idle-change` triggers a buffer check after the editor has been idle
for `flycheck-idle-change-delay`
- `new-line` triggers a buffer check whenever a new line is inserted
into the buffer
Which works with helm as well so we don't need to set it to
magit-ido-completing-read (triggers a warning of magit about
a required third-party we don't need).
Works with magit-next for now.
Tests to update and evilify functions robustness need to be improved.
Does not work 100% with magit-mode-map because it is created with
`make-keymap` and not `make-sparse-keymap` and `map-keymap` does not
seem to work with `make-keymap`.
Set git-use-magit-next to t in the layer variable to use it.
For now magit-ghpull from github layer is disabled.
A LOT of issues with next magit and evil remain to be fixed
Since we can use helm-gtags to jump to any valid symbol on
shell/compilation buffer. For example, if a test case fails and it
outputs a function where the failure occurs, we can move point on that
failed function and jump directly to it.
- Use =L= instead of =l= for ~cider-inspector-pop~.
- Add `cider-inspect` key-binding mention in README
- Add key-binding for `cider-debug-defun-at-point`
Bindings are technically for lisp-mode and scheme-mode rather than
slime-mode since evil-leader/set-key-for-mode doesn't seem to work
with minor modes.
In Finnish/Swedish/other keyboard layouts the `option` key is needed to
type some common characters such as `{[]}~` (#973) so make mapping it to
`meta` conditional.
This commit enables syntax highlighting for Puppetfiles via the
puppetfile-mode package.
A Puppetfile is the configuration file used by librarian-puppet and
r10k for Puppet module management a la Ruby's Bundler.
- lists were not correctly indented sometimes
- **note** and such things do not exist in org
- Note and Important
- Change Feature list to heading
- Change TODOS to actual org TODOS
- Add TOC to python layer
- list indentation
- some typos I could not leave unchanged
- TODO formatting
- List indentation
- typos
- wrong markup
fix conversion issues
Since both offer the same functionality, but except for staging hunk but
it works only with Git anyway.
diff-hl has the advantage that it is usable with left/right fringes and
margin in a single package. Also it does not have the bugs that
git-gutter is having.
