[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
minibuffer-completion-help, metadata and determining completions sort or
From: |
T.V. Raman |
Subject: |
minibuffer-completion-help, metadata and determining completions sort order |
Date: |
Sun, 19 Jun 2011 09:32:34 -0700 |
Stefan, So the metadata gets placed as a property on the table?
Also I said the list would get traversed even if the sort
function was identity because the code does a funcall of the sort
function provided, but perhaps that's not a big issue. Some
examples on providing metadata would really help -- I've never
fully understood the completions code -- especially with respect
to the table and mode arguments.
--
Best Regards,
--raman
On 6/18/11, Stefan Monnier <address@hidden> wrote:
>> I'm having a hard time understanding how one provides custom
>> metadata to completion-all-completions and friends.
>
> The completion table needs to provide the metadata.
>
>> Isuppose I could provide a no-op sorter once I figure out to
>> supply the metadata; however that still feels wasteful since we
>
> If the sort function is `identity' it will leave this as-is.
>
>> would end up traversing the list of completions for no reason ---
>
> Why would you think it needs to traverse the list of completions?
> [ Not that it would matter anyway, since the list has already been
> traversed before and will be traversed again afterwards, any
> potential slowdown should be negligible. ]
>
>
> -- Stefan
>