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.
Emacs 29 with PGTK's kill-new doesn't return its STRING argument (with
the default settings) anymore, so we explicitly pass the file path to
prevent the confusing message "Copied path to clipboard: nil".
Doom changes user-emacs-directory (see 46844b5 for explanation), so
doom-emacs-dir should be used to refer to your $EMACSDIR instead.
Fix: #6530
Ref: 46844b55de
Evil may not always be available in all buffers, and in line with the
filepath yank commands on SPC f y/Y, I thought this command could be
useful. However, I omitted a "replace buffer with paste" command because
in any editing context, evil should be available, in which case it'd be
redundant with `vigp` (or yig for yanking the buffer).
Close: #5281
Co-authored-by: Alex Palaistras <deuill@users.noreply.github.com>
...Rather than current directory.
While +default/search-project-for-symbol-at-point should operate out of
the current project's root, +default/search-notes-for-symbol-at-point
must operate out of org-directory, and no where else, even if
org-directory is not a valid project. 411ed0c8f8 was written to fix
that, but it indirectly broke
'+default/search-project-for-symbol-at-point' (causing it to always
resolve to the current directory, rather than the current project's
root).
Amend: 411ed0c8f8Fix: #5831
Commands that delegate to `+default/search-project-for-symbol-at-point`
to search a directory (like +default/org-notes-search) would not scope
searches to default-directory.
+default/yank-buffer-path-relative-to-project: with non-nil prefix arg,
copy the file name relative to the project root's parent.
Sometimes we also want to specify the project name to let others know
which is the currently mentioned project.
Since multi-line inputs are useless to consult-line and swiper, I've
changed +default/search-buffer to be more DWIM (do-what-I-mean). i.e. if
a selection is active when invoking it, and...
- The selection is multi-line: restrict the search to that region.
- The selection is *not* multi-line: use the selection as the initial
input.
- Otherwise, search the whole buffer as normal.
Unify flycheck-list-errors and flymake-show-diagnostics-buffer under
+default/diagnostics, and use consult-lsp-diagnostics if the lsp and
vertico modules are active.
+default/search-buffer now correctly uses the active selection when
invoking `consult-line` (on 'SPC s s' or 'SPC s b').
Close#5406
Co-authored-by: Sævar Berg <saevarb@users.noreply.github.com>
- Rename module from `:completion selectrum` to `:completion vertico`
- Rename all files involved
- Do *not* yet rename all the functions, as that messes up git's rename
detection.
some doom functions check the completion module with `fboundp`'s instead
of `featurep!`, and counsel can be loaded by using e.g. `lispy`. we add
temporary fixes for this by checking for selectrum stuff first, but this
should be given a more robust fix later on
also we document the selectrum PR's hacks in the TODO.org
see discussion on #5013
- add missing emacs bindings
- properly feature guard swiper related bindings
- for selectrum, unbind `SPC s B` and temporarily bind `SPC s s` to
isearch to prevent don't get errors until we decide what to do there.
- update readme to reflect that
other +default/search-... convenience methods already support
Selectrum explicitly, so perhaps there's a good reason not to
do the same for +default/search-project-for-symbol-at-point?
Changes the behavior of
doom/backward-delete-whitespace-to-column
to only delete to the closest tab column if there
is only whitespace between point and BOL.
This coincides with what the comments state to be
the original intent.
The prefix arg for +default/search-project is intended to enable the
user to pick search location, however when it propagates to the ivy
search function it turns on the "search ignored files" functionality,
which us typically not intended and, furthermore, can be (if desired)
turned on simply by typing the search command in, for exampe,
counsel-rg's case as `-uu -- mysearchterm`
