bug#61532: 30.0.50; [PATCH]: Make completions without sortText fall to back of the list

[João Távora]

On Tue, Feb 21, 2023 at 2:08 PM Augusto Stoffel <arstoffel@gmail.com> wrote:

> > Regardless, there is nothing flex can or should do here, except --
> > as I mentioned -- guessing how the pattern should be painted on
> > the completions.
>
> I think (based on pure guess) that the glorified TAGS do exactly the
> opposite (which is also far more useful): if this is context to enter a
> {color,function,animal}, then return all known colors, function or
> animals respectively (no filtering).

We have different understanding of what "glorified TAGS" are.
Indeed it's the first time I heard the expression and I was just
going on a guess of what it might mean for you.  Anyway, for me,
TAGS is a global thing: it has no understanding of "context",
just an understanding of the literal characters that immediately
precede point.  Such a server matches these characters to a global
list and returns the result.

I agree that using context is far better.  This is what most servers
I know do.  They analyse the code and the contexts and provide
working completions for those contexts.  But I wouldn't call these
servers "glorified TAGS.

> Just checking, because you seem to say the opposite: does Eglot work
> correctly in that situation?

I guess it should...  But speculation is not very useful.  Show me
a reproducible example where it doesn't and it'll be more useful.

João