Comment by tmtvl | Hacker News Reader

Comment by tmtvl | Hacker News Reader

> Recommendation: Use the built-in (vertical-fido-mode). If you want something more, look into Vertico.

I dunno about fido-mode, if I were to recommend a built-in completion package I'd rather say icomplete is better (using icomplete-vertical-mode). It has the neat lazy-completion feature that Emacs and Zsh have where I can type '~/.c/r' and it shows me all possible completions (so both '~/.cache/rofi.druncache' and '~/.config/rofi/config'), rather than eagerly completing on the '.c/' and leaving me stuck in '~/.cache/'.

That being said, I don't see the problem with declaring config bankruptcy, it gives me the chance to avoid making old mistakes in exchange for making exciting new mistakes, which I can learn from.

Yup, agreed. Here's a snippet courtesy of Xah Lee:

(when (>= emacs-major-version 28)

  (setq completion-styles '(flex))

  (icomplete-vertical-mode 1))

FYI, the 1 is never necessary for turning on a mode.

  (icomplete-vertical-mode)   ;; Turn on
  (icomplete-vertical-mode 0) ;; Turn off

I thought that invoking the command without an argument toggled it between off and on, but apparently that's only when it's invoked interactively.

This used to be the case until Emacs 24.1, in 2012.

    Passing a nil argument to a minor mode function call now ENABLES
    the minor mode unconditionally.  This is so that you can write e.g.
    
        (add-hook 'text-mode-hook #'foo-mode)
    
    to enable foo-mode in Text mode buffers, removing the need for
    'turn-on-foo-mode' style functions.  This affects all mode commands
    defined by 'define-minor-mode'.  If called interactively, the mode
    command still toggles the minor mode.

> That being said, I don't see the problem with declaring config bankruptcy

The downside is, that it costs time and attention.

Reply on news.ycombinator.com