swiper VS consult

This is a good improvement. Personally though I left isearch behind. For further search convenience / functionality I highly recommend swiper.

Next you "only" have to remember (elisp) function names. "Completion UIs" like ivy/counsel, icomplete, helm or vertico/consult, give you a nice auto completion list on M-x (choose the one of them, you like the most). Some of those Completion UIs will display existing keybindings and a short documentation for commands, near the auto complete candidates. So you will start to remember more keybindings without "learning sessions", just because invoking functions via keybindings is much faster (more convenient).

Proposal 4 (group-function). This one is an actual addition, which allows candidate gouping in the style of Helm. Note that it is a pure addition. Completion UIs and completion packages work perfectly fine without it. It wouldn't be difficult to add support to Ivy. I wrote the patch.

For the unfamiliar, Swiper is a part of Ivy which lets you search through your buffer with a preview of match candidates: you type some text you're looking for, and up pops a list of matching lines in the minibuffer that you can then use the arrow keys, C-n C-p etc. to scroll through and select the one you want.

When I started using Emacs I was following the setup outlined by System Crafters, which I still think is a really good introduction. But, over the last few months I've started to replace packages with more "minimalist" or "stripped down" packages. I've switched from Ivy and Counsel to Vertico and Consult, and recently I switched from company to corfu for auto-completion.

Ah, neat. I hadn't considered appending comments for searchability. I'm currently getting searchabiity from M-x dwim-... and ivy completion.

Great question. I have one big file with a few hundreds book and quotations from them. Problem is with newlines. When I copy text from kindle it doesn't have newlines because it's depends on font size. So every quotation from book is on one line - could be few thousands chars. I use visual-line-mode and there is a big problem with that. Like swiper would just freeze your emacs if you try to search. https://github.com/abo-abo/swiper/issues/925 Anyone have same problem?

It’s very hard to describe without a visual but the gist of it is that the combination of the following 3 packages make it possible dynamically create queries, refine the results to precisely what you want, and then either perform some action on them or just plop them into a buffer for later use. There’s some notion of a type of the result, which means that the actions and results can be richer than just plaintext. Ie: you can imagine a query over a list of commits, where it displays while you’re searching as only the commit shortrev and subject, but where you can viably define a filter on the commit date or commit author. You can then export that list to a temporary buffer, and pressing enter on any given commit will show you the full diff and the full commit message.

https://github.com/minad/consult/

https://github.com/oantolin/orderless/

https://github.com/oantolin/embark/

That's fair, I see many examples in this thread where people, like you, pass an exact string directly to grep. I'm an avid grepper, but my grep tool [1] translates spaces to ".*?", so I would just type "func lart(" in that example and it would work.

[1] https://github.com/minad/consult/blob/screenshots/consult-li...

BTW, as an alternative to swiper, you can check out consult-line and related commands from consult.

Consult is what you are looking for: https://github.com/minad/consult In particular try consult-ripgrep

Emacs has code peek.

With lsp-mode it has that little window: https://emacs-lsp.github.io/lsp-ui/#lsp-ui-peek

Personally I use eglot with consult which temporarily switches the entire buffer to do the "peek" functionality rather than popping up a tiny window: https://github.com/minad/consult

Thanks for working on this! I just added a consult--maybe-recenter function in a recent commit. This is a nice idea since it can reduce the jumpiness of Consult preview quite a bit.

An example relevant to your list would be some changes many people are taking with their completion framework - using package that leverage core emacs functionality rather than replacing it with a complete package that 'overrides' it. Consult, vertico, orderless and associate packages come to mind here. If you do a bit of a search you'll find plenty of info. Here is a video from Prot on the subject, but there are many others as well. I think Prot actually went on to write his own completion system to overlay native emacs functionality as well.

For the "lauch workspaces", I use burly which just uses simple bookmarks. Then with consult, I just use C-x b, then m to narrow to bookmarks and I have all the workspaces available (remote as well).

Wow, interesting that my response is getting down voted. It seems not enough that I give away my work for free. Nevertheless I appreciate support from the community, as other Emacs package developers. The support is actually helpful. To clarify, publishing my configuration would translate into quite a bit of work, requiring separation of private and public bits.