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.
By default the only available checker in `react-mode` is
javascript-eslint. `javascript-standard` is based on `javascript-eslint`
and has some modification on rules. Since it's not defined as a checker
for this mode, it's also impossible to select it in a buffer.
As reported in #5694 dash layer cannot be configured according to the
documentation. This commit fixes that, and allows you to actually define docset
path with `helm-dash-docset-newpath`. It also defines more sensible default for
docset `~/.docsets`, which is the default path for helm-dash.
Fixes#5694
You have to replace in your dotfile the layer variable
colors-enable-rainbow-identifiers t
by
colors-colorize-identifiers 'all
color-colorize-identifiers can take 3 values:
- variables -> colorize only variables via color-identifiers mode
- all -> colorize all identifiers
- nil -> no colorisation
New key bindings:
SPC t C a -> colorize all
SPC t C C-a -> colorize all globally
SPC t C v -> colorize variables
SPC t C C-v -> colorize variables globally
Per syl20bnr's comment on PR 6192, the package should always be
installed with the colors layer, but only hooked into prog-mode when the
variable is active. Renamed the variable
colors-enable-rainbow-identifiers-by-default to clarify this, and
modified the documentation.
When Spacemacs encounters a large file it displays a
prompt to open the file literally. However, if the file
is opened as a result of another action (e.g. Visiting a
TAGS table) it might not be obvious which file is triggering
the prompt. This change adds the file name to the prompt.
