I intend to eventually replace projectile with project.el, so these
doom-projectile-* variables need to be generalized, starting with the
fd/ripgrep executable paths.
ALong with that, this refactors Doom's projectile-generic-command to
lean more on built-in fd support in projectile, where possible (fewer
wheels reinvented).
Ref: doomemacs/core#1
We were using `shell-quote-argument`, which is meant for passing file
names, strings and so on, not command-line arguments. For example,
`(shell-quote-argument "--foo=bar")` yields "--foo\\=bar", which is
obviiously invalid unless we're trying to pass an option named '--foo\'.
At any rate, there is no quoting/escaping for shells in the default
value of `consult-ripgrep-args`, so it doesn't look like this is
something we need to do.
featurep! will be renamed modulep! in the future, so it's been
deprecated. They have identical interfaces, and can be replaced without
issue.
featurep! was never quite the right name for this macro. It implied that
it had some connection to featurep, which it doesn't (only that it was
similar in purpose; still, Doom modules are not features). To undo such
implications and be consistent with its namespace (and since we're
heading into a storm of breaking changes with the v3 release anyway),
now was the best opportunity to begin the transition.
When selecting a buffer in another workspace with
+vertico/switch-workspace-buffer, that workspace will be switched to,
instead of opening the buffer in the current workspace.
+vertico/switch-workspace-buffer was hardcoded to only list buffers from
the first 9 workspaces. This removes that limit.
Minor catch: workspaces beyond 9 will use lower case a-z as narrowing
keys, followed by upper case A-Z. There will not be any valid narrowing
keys beyond 61 workspaces -- but who in the world would have that many?
Previously, +vertico/embark-export-write doesn't let embark execute
other added hooks in embark-after-export-hook.
Add the edit command at the end of the list because other hooks may
assume that the buffer isn't yet editable.
BREAKING CHANGE: This commit changes the behaviour of the TAB and RET
keys in a consult-completing read multiple session, in order to make
them more intuitive. The behaviour is now:
- TAB: (unchanged) always select or deselect the current candidate, and
if the candidate is selected, move the index to the next one (this
allows for pressing TAB repeatedly to select multiple subsequent
candidates).
- RET: If no candidates have been selected, select the current candidate
and exit the completion session. If some have been selected, disregard
the current candidate and exit.
- S-TAB: (new) like TAB, but the keeps the input.
Embark adds easier prefix-argument and digit-argument insertion in
embark-act, but these clog up the space in the which-key indicator
Also update the embark-become test to the new target format.
The vast majority of Doom modules have their defadvice! statements in
their config.el files, and not their autoloads. Since these don't need
to be autoloaded to function, we move them for better consistency.
- fix a paren error in the function that caused the buffers to be sorted
alphabetically and not by recency
- refactor the workspace buffer sources to use consult--buffer-query,
that way we get niceties like the current buffer being last
Fix#5366
embark targets changed internally to plists a while back. This didn't
really seem to break anything but it's best to be up to date with the
upstream representation.
BREAKING CHANGE: remove +vertico/(next|previous)-candidate-preview.
BREAKING CHANGE: Move vertico-(next|previous)-group to C-M-j/k now that
C-S-j/k now default back to scrolling up and down pages.
Update docs to reflect these changes.
Switch from the homemade +vertico/backward-updir to the upstream
vertico-directory-delete-char. The former has the nice feature of
traversing up abbreviated paths, but this comes at the cost of not being
able to fully erase the path (since the buck stops at /), and
unintentional directory moving in commands such as +vertico/find-file-in
which causes issues. Overall this minor convenience is not worth it, so
the vertico-directory-delete-char behaviour of just deleting up to the
previous / is preferred instead.
