tag autocomplete select list sorted by best match and/or last use

[miroklarin]

---

tangent: v0.8.3 AppImage

Use case

Working on idea on few related notes I tend to use same or similar nested tags, either for as document or inline.

Example

Working on bash scripts project.

Tags that I might use in all notes containing bash in the tag:

• #bash, note tag for wiki or project notes about bash
• #bash/list, inline tag in any note ("how to" snippets...) dealing with bash list
• #lang/bash, inline tag for tips and tricks snippets in bash in any note
• #dev/parser/bash, inline or note tag for solution in bash

(those are just examples, I try to use more flat than nested tags, but sometimes I just have to sub categorize)

As I'm writing, tag auto complete helps a lot, but it is not reliable and requires constant checking and correcting.

Current behavior

Start typing bash in search field or inline inside the note.
Dropdown selects for example #lang/bash.
As soon as I type / it autocomplete #lang/bash, but what I actually typed is #bash/.
If it autocomplete, I need to delete and select correct tag from dropdown.
It requires paying a lot attention what is currently selected in dropdown and it doesn't match what I see inline on the screen.

It looks like tags are sorted by number of usage or something like that as I noticed that sometimes another tag is selected or they are rearranged after I remove or change tags on more notes, so selecting correct tag from the list is not always same.

Expected behavior

I would expect that what I typed inline is source of truth and if there is no match to offer me closest match, or at least if I press / it doesn't change what I previously typed.
So if I type #bash/ I would expect first two choices to be bash/list and bash, but not lang/bash or dev/parser/bash which is even worse to correct.
Other matches that do not fully match input text could be sorted by last use.
In this case if dev/parser/bash was used recently it would be above lang/bash.

[taylorhadden]

This is a good one. It sounds like you want / to just not cause autocompletion. I think that's pretty reasonable.

The other issue describe sounds like a sorting issue. I definitely agree with what you expect the behavior to be. I'll have to investigate further.