I got an idea — I think it should be "Force except for current path". This way I can just bind it to a new tab open and the only duplicate tabs left after this operation would be the last two.
Unfortunately, that's rather inconvenient as I'd lose my current path — and the main reason I'd open a new tab instead of my favorite folder (either via Winkey+# shortcuts or by just alt-clicking on the favorite list in the tree view) is precisely because I need to navigate around current path, i.e. when a few "go up/select another folder" commands are faster than starting from a favorite folder position.
Thank you for the tip, at the moment it seems even worse than having Ctrl protect the path as it means none of the other duplicate tabs will close. But maybe if I disable qualifiers and add your command to run after closing a tab, that could be a temporary solution
Yes, it's an additional condition to a) that would make the script behave like I would ideally like it to behave.
Let me clarify this point. If I Ctrl-T a new tab, this path will get "protected" (assuming qualifiers are on), which is nice as it prevents this new duplicate tab TabADup from being closed automatically.
Now suppose I just leave these two duplicate tabs TabA and TabADup hanging there and switch to a different 3rd tab and then invoke CloseTabSiblings. I would like the "path protection" to fade by then, so that any subsequent use of the script would close TabADup. However, this doesn't happen because the path stays protected until the script is restarted, thus polluting my tab space.
Moreover, if I happen to navigate to this path in the 3rd tab, then it wouldn't close duplicates either since this path is protected.
c) there is also a typo, I meant "but NOT on folder changes"