I feel like we should start from scratch on this one and carefully choose the
defaults.
Also this settings is a very personal setting so if we make some buffers
useless we must have a consensus on it. Marking all special buffers starting
with `*` as useless is too aggressive and make Spacemacs less POLA since two
consecutive press on SPC TAB may not revert to the original buffer.
Define a new custom layout named "@Notmuch" with binding "n" for notmuch
buffers. The custom layout's name can be customized using the new
notmuch-spacemacs-layout-name variable. The custom layout's binding can
be customized using the new notmuch-spacemacs-layout-binding variable.
- Make the notmuch layer more idiomatic.
- Move org related stuff to a use-package hook for org.
- Simplify configuration of helm and ivy
- Sort package config
- Move sections in README to avoid repetition of Evilified State sections
- Add docstrings to functions and use // convention for private function names
This patch adds a notmuch[1] layer to Spacemacs!
notmuch is a mail indexing system written in C. It provides an emacs
interface, and this patch adds Spacemacs support for this interface.
Thanks to @FrancescElies for starting this work, and working with me to
get it finished. We have been using the layer for awhile now and are
happy with the initial release!
Closes#2163
[1] https://notmuchmail.org/
Tested-by: Francesc Elies <elies@posteo.net>
Tested-by: William Casarin <jb55@jb55.com>
Signed-off-by: William Casarin <jb55@jb55.com>
org-mu4e was already handled in the mu4e layer which is the correct place for
this.
Added notmuch to mu4e layer, maybe not the right place for this but for now
it is OK.
Mark up code that is mentioned in the documentation of some readmes.
In the case of “long options”, like for example `--with-emacs`, this is not just
cosmetic. On GitHub, Org files are apparently rendered in such a way that
strings like `--` in non-verbatim text (i.e. not verbatim-quoted nor
code-quoted) is transformed to `–` (EN DASH U+2013). So the string:
… --with-emacs option:
Will show up like this:
… –with-emacs option:
Also mark up nearby not-marked-up code mentions. But this pattern was what was
searched for, so this mostly changes the abovementioned kind of thing.
By convention, code markup (`~`) is reserved for keybindings in Org-based
documentation in Spacemacs. Verbatim markup (`=`) is reserved for code and
other code-like things. So change several readmes to reflect this convention.
Use verbatim markup for things like (non-exhaustive list):
- Emacs Lisp functions, modes, buffers, etc.
- Environment variables
- Directory paths
- Code in general
This commit adds a custom layout for mu4e related buffers. Four different major
modes are used in mu4e buffers based on their purpose, so a function is used to
add buffers in these modes to the new layout. This setup is largely based on
that of the ERC layers custom layout.
Currently, in multi-account mode, the mu4e layer guesses which account
to use to reply a message by its "maildir". However, some messages may
be forwarded and may need to use the original email address to reply.
This commit detects whether such an email address is defined in
"mu4e-account-alist", and uses that to do the replying if possible.
This commit deactivates account selection and switching support if the
account list isn't defined. We also don't need the follow-up action of
undoing the account selection changes, so we can just skip both of the
hooks.
This is useful for users who only have 1 account - they don't need the
helm popup to select which account to use. They can just define the
variables outside of the `mu4e-account-list`.
- Clarify installation instructions
- Bring README in line with conventions
- Create layer variable for installation path
- Move mu4e-account-alist to config.el
- Move extensions.el to packages.el
- Define mu4e as built-in and not local
- Add commands to ensure mu4e is deferred
Helm seems to treat "!" specially in pattern matching, so having a ! in
the pattern string when traversing directories is problematic. This
change fixes#2737, because as far as I can tell "+" has no special
meaning in a helm pattern.
Of course, we can choose a different character, but I'm fond of "+" as
representing "more layers here".
