Subject: bug#45260: 28.0.50; Maybe flex should only sort when there is no sorting metadata?

From: Dmitry Gutov <[email-masked]>
Date: Tue, 28 Sep 2021 02:11:59 +0300

On 17.08.2021 19:38, João Távora wrote:
> Dmitry Gutov<[email-masked]>  writes:
> 
>> On 17.08.2021 17:05, João Távora wrote:
>>> On Tue, Aug 17, 2021, 13:43 Dmitry Gutov <[email-masked]
>>> <mailto:[email-masked]>> wrote:
>>>      On 17.08.2021 13:41, João Távora wrote:
>>>       > I've
>>>       > not seen an example of a table where its original sorting
>>>      mattered more
>>>       >_when_   there is some search pattern.
>>>      Do you have examples of completion tables which do specify
>>> sorting, but
>>>      where flex sorting obviously should take precedence?
>>> No, do you? Love to see them, or the converse. But does it matter?
>>> Flex is for searching with patterns, stable sorted by scores,
>>> solving ties with whatever sort order came first. Dmitry/flex, or
>>> Flix, or Flax, may be something else, you understand? It's by design
>>> like this.
>> If there aren't any such significant cases, flex could do what Omar is
>> suggesting, solving the reported problem with no real downside.
> OK. Let's see the code and then it's easier to evaluate if there's "no
> real downside".  If it's indeed true, than no problem.

Please go ahead and fix your own code in any way you like.

Here's an example of user confusion that the current behavior invokes:

https://github.com/company-mode/company-mode/discussions/1223#discussioncomment-1387929