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.
+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.
- 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?
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`
Affects doom/browse-in-other-project, doom/find-file-in-other-project,
+default/search-other-project and
+default/search-project-for-symbol-at-point.
When performing a text or file search in "another project", prior to
this update the current project would be the first highlighted
candidate, which doesn't make much sense when you're invoking a command
for searching *other* projects.
