• 0 Posts
  • 6 Comments
Joined 1 year ago
cake
Cake day: October 16th, 2023

help-circle

  • /u/hvis Would you consider changing this, since this way of deduplication in the frontend is quite inefficient? Given that the default completion UI demands that candidates are unique with respect to equal and even deletes equal duplicates, the backend should better produce unique candidates.

    Deduplicating in the backend is not difficult, all that is needed is adding a suffix like (1), (2), (3), … In fact, this is what I am doing in my Consult package, which also is a backend and provides completion tables. For example for the consult-line command I was facing the same issue, that candidates must be unique with respect to equal and not to eq.

    cc /u/JDRiverRun




  • One should also mention the relatively new vertico-suspend command. It takes a different approach via recursive minibuffers, but has its own limitations.

    I would guess that vertico is not always able to repeat extended commands properly and so they are disabled by default.

    No, see my other answer.

    Unfortunately, if you must have such a feature in full generality, I’d recommend that you use helm or ivy instead.

    Ivy and Helm do not support repeating arbitrary completion sessions in full generality - because it is hardly possible. Only the state of commands which go through the ivy-read or helm API can be fully reconstructed.