[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Programmed completions are utterly confusing

From: Stefan Monnier
Subject: Re: Programmed completions are utterly confusing
Date: Mon, 14 Nov 2022 21:55:52 -0500
User-agent: Gnus/5.13 (Gnus v5.13)

> - Use case I have right now: I want to search through URLs and their
>   page titles. If I put each url into the main display string, and

"search" doesn't really make sense for the completion code, because
completion is about helping you complete a string S to a "more complete
version of S".  So typing text that's not in the final result goes
against the design.

If you want, you can provide a *completion style* which can match the
input string against the set of completions *and* their annotations.

I think you're thinking of completion UIs based around the idea of
selecting one of a set of candidates.  Some of the completion UIs indeed
do that, but the core completion framework and the completion tables are
not designed specifically for that.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]