A warning gets logged if a lazily-loaded evil-collection package is
loaded too early at startup, but the goal posts were in the wrong place,
resulting in unavoidable warnings for packages that weren't actually
loaded too early.
Slipped by manual testing due to consult not being loaded at the time
and doom--help-search going to default grep-find usage instead of
hitting the failiure.
Amend: 54c4340740
In the Elder Days, it was common to give Fortran files the extensions of
`.FOR` or later `.F90`. The major modes for Fortran don't automatically
detect this conversion. The former was already accounted for in Doom's
module, but not the latter. This commit rectifies this.
Let's not hide the minibuffer. It may be detrimental in cases where
certain helm commands actually display helpful information there. And
rather than design edge cases for a package I don't dogfood, and push
minimalism onto helm users, I'll lean onto the defaults more instead.
Ref: #6676
Co-authored-by: johanwiden <johanwiden@users.noreply.github.com>
Describes how to disable synchronization between the kill-ring and
system clipboard.
Close: #6947
Co-authored-by: rittelle <rittelle@users.noreply.github.com>
Some unknown difference between `loaddefs-generate` (Emacs 29+) and
`make-directory-autoloads` (<=28) causes evil-pinyin's autoloads file to
throw an error in 29+ when loaded, complaining about missing macros
defined by its dependencies (mainly `define-namespace` and
`evil-define-*`). Specifically, void-function errors.
Since the package is loaded almost immediately on startup, evil-pinyin's
autoloads file isn't needed in the first place, so by disabling it, the
error is resolved. This'll do until I can find a better solution or, at
least, the right party to report it to.
Ref: #6482
- Advise orderless to use pyim-cregexp-build when using vertico
- Add it to ivy-re-builders-alist when using ivy
Close: #6482
Co-authored-by: merrickluo <merrickluo@users.noreply.github.com>
Invoking +lookup/documentation in shell-script-mode will yield an "X man
page formatted" in the minibuffer with no man page popup. It must be
invoked a second time to see it. This commit fixes that.
If an org-capture template generates a new, blank file, Doom steps in to
insert a yasnippet file-template into the buffer. If the file template
has text fields, it leaves the new buffer in an "editing snippets"
state (and insert mode) which causes errors downstream when org-capture
tries to modify the buffer.
The file-templates module employs some heuristics to prevent false
positives like these, but packages (and org-capture) can get around this
by simply generating and switching to the org buffer before modifying
it. This commit no-ops file-template expansion in any org-capture
session, which should resolve these issues.
Fix: #6160Fix: #6741
Because company-yasnippet expands each snippet to produce a preview in a
temporary (and fundamental-mode) buffer, java-current-class and
java-current-package throws errors, so I've added a special case to
return a placeholder if expanded in a temporary buffer.
`doom doctor` throws a type error for enabled modules without a
doctor.el and/or packages.el file. This occurs because, in
in775ee2f04aad, `doom-module-expand-path` was changed to return nil if
the target file did not exist, and the doctor wasn't updated to handle
this. It passes `nil` to `load`, causing this type error.
Amend: 775ee2f04a
