selectrum VS vertico

Selectrum's wiki has some basic info on completing-read: https://github.com/radian-software/selectrum/wiki/Tips-for-Creating-Commands

[1] https://github.com/radian-software/selectrum/issues/114

I noticed over the weekend that the venerable Selectrum package made by Radon Rosborough has been deprecated in favor of Daniel Mendler's Vertico package.

https://github.com/radian-software/selectrum is getting superceded by https://github.com/minad/vertico within just a year or two.

I have been using straight for a while now and I think it is great! The ability to lazy load everything by default does a lot to make Emacs snappier (or at the very least, faster to boot). Being able to pull packages directly from git (be it local or a forge) makes package development a lot easier. raxod has a lot of really sleek, modern emacs packages that I would encourage everyone to check out, spectrum[0] and ctrf[1] in particular are really great as well.

[0] https://github.com/radian-software/selectrum

selectrum

;;https://github.com/raxod502/selectrum (defun force-debug (func &rest args) (condition-case e (apply func args) ((debug error) (signal (car e) (cdr e))))) (advice-add #'selectrum--minibuffer-post-command-hook :around #'force-debug) (selectrum-mode +1) ;; to make sorting and filtering more intelligent (selectrum-prescient-mode +1) ;; to save your command history on disk, so the sorting gets more ;; intelligent over time (prescient-persist-mode +1) (setq completion-styles '(orderless)) ;; Persist history over Emacs restarts (savehist-mode) ;; Optional performance optimization ;; by highlighting only the visible candidates. (setq orderless-skip-highlighting (lambda () selectrum-is-active)) (setq selectrum-highlight-candidates-function #'orderless-highlight-matches) (setq selectrum-prescient-enable-filtering nil) (selectrum-prescient-mode +1) (prescient-persist-mode +1) (use-package marginalia :ensure t :config (marginalia-mode)) (use-package embark :ensure t :bind (("C-." . embark-act) ;; pick some comfortable binding ("C-;" . embark-dwim) ;; good alternative: M-. ("C-h B" . embark-bindings)) ;; alternative for \describe-bindings' :init ;; Optionally replace the key help with a completing-read interface (setq prefix-help-command #'embark-prefix-help-command) :config ;; Hide the mode line of the Embark live/completions buffers (add-to-list 'display-buffer-alist '("\`\Embark Collect \(Live\|Completions\)\" nil (window-parameters (mode-line-format . none))))) ;; Consult users will also want the embark-consult package. (use-package embark-consult :ensure t :after (embark consult) :demand t ; only necessary if you have the hook below ;; if you want to have consult previews as you move around an ;; auto-updating embark collect buffer :hook (embark-collect-mode . consult-preview-at-point-mode))`

Selectrum and Prescient would be nice.

It would be great if you add your snippet to the Vertico wiki. Such tweaks can be quite instructive for others who want to achieve the same or similar effects for other completion commands.

If you want completion to be sorted by your "most recent" I suggest you have a look at completion libraries. One example is vertico; when you enable savehist mode, the variable magit-revision-history, containing the branches you visited is persisted between sessions and vertico use that offer completions by most-recently-used, by default.

I think vertico is best alternative recently, really fast on Linux, macOS and Windows.

(use-package modus-themes :vc (:url "https://gitlab.com/protesilaos/modus-themes" :branch "main")) (use-package vertico :vc (:url "https://github.com/minad/vertico" :rev :newest :lisp-dir "extensions/"))

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.

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).

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.

I thought that lsp and rtags were different tools to do different things. Regarding lsp, I configured lsp-mode in my init file indeed! Currently I'm using Vertico (plus recommended sub-packages at github repository) and lsp-mode.

Hey! There has already been a horizontico.el. ;)

FYI, selectrum is getting deprecated in favor of vertico. https://github.com/minad/vertico/issues/237