Re-implemented

[elig0n]

Hi,

I've re-implemented the main functionality of the script by using the callback's activeInfo object properties instead of sort.
This should provide better speed as it does not need to fetch & sort the whole list of active tabs with every tab event.
It also solves issue #1 where background tabs are mistaken to be last activated.

P.S I have commented out the callback's wait() call because it proved to be unnecessary on my system besides also creating a noticeable lag with the somewhat high value 300 that it was set to initially.

Let me know what you think

[davidsierradz]

Hi, thanks for this!

I don't remember the exact details of why I chose to implement it that way (with getSortedWinTabs). If my memory doesn't fail me, it was because Tridactyl implemented the alternate buffer (# or :help alternate-file) with that helper function: tridactyl/excmds.ts at a1c5201142bffe4a0f027694dfce22eee9708d9b · tridactyl/tridactyl.

Also, I think I was also using Ctrl+Tab cycles through tabs in recently used order option. So when I open a tab in the background, and you press <C-Tab> it goes to that recently opened tab, check this:

I'm guessing that the primary reason I developed this extension was to always have a visual indicator of where I'll land after pressing Firefox's <C-Tab> or Tridactyl <C-^>/:buffer #

I guess the Venn diagram of TST, Tridactyl and weird <C-Tab> users is very small.

About the callback's wait(). I developed and used this extension in a crappy and extremely slow dual core atom and mechanical disk laptop, without it I was having randomly sync problems and bad results. This doesn't happen anymore (yay!).

I'm not using Firefox or TST much these days (qutebrowser fanboy now), so I'm don't have a dog in this fight. Just stating where I come from. ¿What do you think?

Thanks again.