tiebreak index does not exist

[valpackett]

The readme says

There are five sort keys for results: score, index, begin, end, length, you can specify how the records are sorted by sk --tiebreak score,index,-begin or any other order you want.

However…

https://github.com/lotabout/skim/blob/291fc34c58b1670a5e8c95f1e8f930b82c030b19/src/item.rs#L200-L209

index does not seem to exist at all??

[lotabout]

@valpackett It's a doc error. index was removed in commit 94846e7. Can't remember exactly why, but possibly sorting by index could be achieved by --tac.

[blueforesticarus]

Based on the documentation, it seems you are meant to be able to set the priority of tiebreakers by specifying multiple.
From what I can tell, with --tac you cannot sort at all.

This is rather unfortunate, as what I'd really like to do is sort by score, and then by index, so that newest - perfect matches show up first (in this case I am skimming browser history, sorted by timestamp)

[j-lakeman]

Then --tiebreak=index should probably be changed / removed from all shell binding files right? Like this one:

skim/shell/key-bindings.bash

Line 53 in 32d9e70

SKIM_DEFAULT_OPTIONS="--height ${SKIM_TMUX_HEIGHT:-40%} $SKIM_DEFAULT_OPTIONS -n2..,.. --tiebreak=index --bind=ctrl-r:toggle-sort $SKIM_CTRL_R_OPTS --no-multi --read0" $(__skimcmd) --query "$READLINE_LINE"

This would be an ez PR I could provide.

[LoricAndre]

I'd say removing it might not be the best option, but I'd love a PR that readds the index, as long as it includes the necessary tests to ensure that if there was a reason for it to be removed, we find it before it hits the repos.

[LoricAndre]

Note: I think I'll actually try my hand at this one, please tell me if you want to work on it to avoid duplicate PRs !

[j-lakeman]

Go for it!