The precise semantics of use-package's :after keyword is janky (see
jwiegley/use-package#829) and, in the case of 992bd8f7e2, causes
subtle breakage. For one, the remappings in the following :init block
were deferred until embark loaded, so they weren't available at startup,
so they reverted to their old (often vastly inferior) predecessors, like
recentf-open-files instead of consult-recent-files.
Amend: 992bd8f7e2
Currently, embark-consult bindings don't get loaded if consult hasn't
been loaded yet, leading to missing embark actions until the first
manual consult load.
Corfu makes completion-in-region-function a local variable in buffers
where it is enabled, so when this form is evaluated in one of those said
buffers (such as opening a file with Emacs before accessing the
minibuffer), completion-in-region-function will just be set locally
there.
BREAKING CHANGE: `embark-collect-snapshot` has been renamed upstream to
`embark-collect`. Since the `C-s` mnemonic doesn't really make sense
anymore, I've moved the binding to `C-c C-l`, which has the nice bonus
of being next to the similar `C-c C-;`, and being nicer.
`counsel-describe-symbol-function' still doesn't use `helpful-symbol'
because `helpful-symbol' throws up a prompt when the symbol refers to
both a function and a variable.
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.
The C-c C-s binding mirrors the export and writable export bindings.
embark-export is used for type specific exports (such as buffers to an
ibuffer buffer), not for verbatim exports. This is most noticeable if
you want to export a variable list, which gets you to an apropos buffer.
if you just want a list of things to keep around,
embark-collect-snapshot is the tool for the job, but having it be only
on C-; S makes it harder to reach and less visible. C-c C-s is a nice
visible thing to have around.
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.
Fewer links means less confusion.
- Merge doom-issue and doom-commit links into doom-ref (for auto-linking
Issue/PR/commit references).
- Merge doom-module-source and doom-docs-source links into doom-source.
- Rename doom-report-issue to doom-report.
- Use '!' as the icon for module issues link.
- Remove doom-repo (replaced with "doom:*" in :lang org module).
- Add doomdir and emacsdir links to :lang org module.
It was `evil-show-registers' that we wanted, not
`evil-ex-registers' (which never existed in the first place). Folks who
did not have :completion ivy enabled (e.g. vertico and helm users) would
see 'commandp, evil-ex-registers' errors when pressing `SPC i r`. Folks
who had it enabled would transparently invoke `counsel-evil-registers'
instead (because it was remapped).
Fix: #5753
