Is there any option to put new independent tab on top instead of bottom?

[you74674]

There are options to control the behavior of new inserted child tab, like "the top of the tree" or "the end of the tree",
I want all new independent tabs to be on the top of the "root tree".
Is there any way to achieve this? It seems like there's no option about this.

[piroor]

No such option for now, and I have no plan to implement it as a built-in feature, because it looks beyond TST's project scope. I think it can be done by something other extension (I don't know any existing implementation, and it may be developed as a new helper addon for TST) and I'm welcome to update TST compatible with such an extension.

[johnbwang]

Awesome! My add-on is now updated. @you74674, update both TST and new-tabs-first to fix the startup issue.

[you74674]

Thank you!
When there are too many tabs opened, it seems like the order of the process can still go wrong. When I try to restore a closed tab(in a tree), it will be inserted to the correct position first, and then moved to the top even though it should be in a tree.

[johnbwang]

@you74674 Okay, I'll take a look. We should continue the conversation at johnbwang/tst-new-tabs-first#1 since it's not directly related to TST.

[cstrahan]

@piroor message.tab.ancestorTabIds.length == 0 when opening a tab through the TST context menu, and also when opening a new tab through the "Open a new tab: Child Tab" key binding, which means that using https://github.com/johnbwang/tst-new-tabs-first/ results in new tabs (in either scenario) being moved as new roots in the tree, whereas I expect them to be children/siblings to the current tab (depending on TST settings).

Is there a way for third-party plugins to detect either scenario?

[cstrahan]

Some other details: #2543 (comment)

[ELLIOTTCABLE]

I took a gander around for other extensions that implement this, but I had no luck.

There's this one, but the advertised functionality doesn't currently work: Tab Open/Close Control by F. Kolbe.

I dived in to attempt to solve this with CSS, but ended up getting a little side-tracked. CSS, however, seems to be the "correct" solution: if you open new tabs at the top, then the index of all subsequent tabs changes every time you open a new root-level tab; you can't develop muscle-memory for, e.g., :tab 26 within a particular session. If you maintain the tab-order, then reverse them on-display, at least some tab-indexes will remain static throughout a session …

It's not perfect, but my current, hacky solution is to reverse the entire ul.tabs using flex-box:

/* Invert order of entire tab-tree.
 * Note: *Also reverses sub-trees*. */
#tabbar #all-tabs > ul.tabs {
  display: flex;
  flex-direction: column-reverse;
}

When I have more time, or get annoyed enough, I may attempt to improve on this such that subtrees are ordered in chronologically-increasing order, but the root tree is ordered in chronologically-decreasing order.

[you74674]

This is an interesting idea, thank you for sharing this!