Notmuch, like org, uses git describe to build a version string variable
at install time, but Doom preforms shallow clones of its packages, where
git describe does not work.
Notmuch is one of our bigger packages and the variable isn't essential
for normal use, so I've opted to build notmuch-version.el by hand. It
lacks the commit offset, but it has enough information to work with.
Fix#5581
At some point in the original PR alerts stopped working. I've finally
tracked down why and found three components to the problem:
- I'm calling `start-process` incorrectly
- `truncate-string-to-width` is called on `nil` when no from name is
given
- mu4e-alert uses :docid to check for duplicates, which is not provided
in mu 1.6, and so :message-id must be used instead.
Overrides ranger-travel to have better mode detection for which
completion framework to use, and default to emacs built-ins instead of
ido.
In theory this should be a temporary fix until ralesi/ranger.el#236 gets
merged, but the maintenance status of ranger.el is not clear.
Fix#5509
Ref ralesi/ranger.el#236
The following functions are affected: `+pass/edit-entry`,
`+pass/copy-field`, `+pass/copy-secret`, `+pass/browse-url`. All of
these functions have counterparts in `password-store`. Additionally, the
functions in password store add git commit messages when files are
changed.
Questions:
- Should we also deprecate the `ivy` and `consult` versions? The
`password-store` versions work perfectly well here with `vertico` (not
sure about `ivy` though).
There weren't enough checks that we were truly in a native-comp build of
Emacs. Not the most elegant solution, but the CLI rewrite handles this
far better so it'll do for now.
Fix#5131
Post-rewrite bin/doom will accept multiple -l's, but for now will only
accept one. This change was made to prepare for the documentation
generator, which will live outside the repo.
Because Outlook interprets 90ch as 90px ... nice job Outlook.
I also adjusted text size and padding with code snippets while we're
tweaking.
Close#5439
This adds support for two new definition types to the left! convenience
macro: defun* and defadvice.
First, defun* is for defining recursive, local functions (uses
cl-labels under the hood). e.g.
(letf! (defun* triangle (number)
(cond ((<= number 0) 0)
((= number 1) 1)
((> number 1)
(+ number (triangle (1- number))))))
...)
Second, defadvice is for defining temporary advice (which has a global
effect; it can later be improved to limit scope by redefining things
with cl-letf). e.g.
(letf! (defadvice my-fixed-triangle (fn number)
:around #'triangle
(funcall fn (1+ number)))
...)
'doom/reload' should and cannot regenerate the user's envvar file,
because it's not typically running in your shell, but it should reload
your existing envvar file.
Fix#5399
Ref #5344
Since the which-key window didn't have focus, its C-h keybinds were
unpredictably unresponsive, making next/previous-page navigation et co
finnicky. This commit restores the needed focus.
Ref https://www.reddit.com/r/emacs/comments/pwr7va/comment/heydq4g
BREAKING CHANGE: If `beancount-electric-currency` is non-nil, the
currency is appended to transactions, falling back to the ledger's
"operating_currency" option, even in cases where a currency was not
explicitly needed (e.g. only one currency specified for an account).
After receiving input from beancount-mode's author, I reconsidered its
utility and decided to remove it.
Ref beancount/beancount-mode#19
Rather than reloading whatever `doom-theme` is set to, reload the
currently active theme(s). Although `load-theme` is advised to change
the value of `doom-theme`, not all theme switching commands use
`load-theme` (e.g. `consult-theme`).
Fix#5539
We couldn't write a popup rule for message buffers because they were
named *X*, where X was the email's subject line. There was no distinct
pattern to target via regex, and the buffer is display before its mode
is initialized, so a more sophisticated popup rule wouldn't work either.
By renaming message buffers *subject:X*, we now have a chance to target
it.
