calendar-location-name comes from solar.el which is neither loaded by
default nor by this layer. Hence it can potentially be void and must
not be accessed directly.
Instead wrap it in bound-and-true-p to guard against it being void.
Add a release note about the limitation of org loading since 0.105, and
also document it in the org-layer's README.
Close#3277
Move note to FAQ and correct text to 0.104
Related to #1296.
Use `SPC a o` as prefix for org related applications like `org-agenda`
or `org-capture`. The `a` is for "application", and `o` for "org". To
avoid long keystrokes for `agenda`, direct bindings are offered through
`SPC a o <key>`.
Because `org-agenda` is one of the principal application, it has be
mapped to repeating the last letter (`SPC a o o`).
In help buffers, TAB in emacs state allows you to jump through the
links. This allows for the same behavior in motion state. This is very
useful for jumping to function definitions.
shell-file-name provides the "best" shell Emacs knows about, i.e. the
login shell from $SHELL, or a system default, which is just about as
arbitrary as the current default to /bin/bash.
This makes all Notes in DOCUMENTATION.org be *Note*: and changes the
markup around the spacemacs init file path in jabbers README.org to
proper org markup.
We need to look for GNU ls after exec-path-from-shell was initialised
and has fixed exec-path. Otherwise the directory containing gls may not
yet be in exec-path
This change add a `switch-to-scratch-buffer` function allowing to – you
guessed it – switch to the `*scratch*` buffer, taking care of creating
it if necessary. The function is bind to `SPC b s`, `b` as it concerns
buffers, and `s` for `scratch`.
This hook is duplicating the functionality of a multiterm hook, causing
it to be called after the multiterm hook has already switched to a
different buffer, thus quitting a job in the latter buffer.
First version of the bepo contributed layer. I'm probably the only one
using it for now, let's wait for issues and contributions!
This is a snapshot-branch of my own development branch, it will not
change, except maybe if it reaches a new "clean" state before it gets
merged.
