If you're really curious, one use case is auto-assigning a tab group. When one makes a frame, the tab bar defaults to showing the window from which it was created and any custom tab-bar symbols attached to the tab have to be recreated. Another use case is optionally keeping tabs "pinned" to their user-specified positions and the post-open hook can help track the first and subsequent positions. I'll surely add more over time. tab-bar is great and fun to use and enhance with cool productivity tools.

On Tue, Oct 29, 2024 at 2:19 PM Ship Mints <shipmints@gmail.com> wrote:

I'm trying to align all tab creation behavior with tab-bar-tab-post-open-functions. Even the first tab should be considered "opened" by the system and call people's functions on the hook. That tab, if you close it, does call the close hooks correctly and that's aligned, at least. If the open hook doesn't get called, then those tabs have to be treated in a special way and that creates bugs and burden. Not sure how relevant it is what I do in my custom hook that should get called for the implied opened first frames but doesn't.

On Tue, Oct 29, 2024 at 2:15 PM Juri Linkov <juri@linkov.net> wrote:
> tab-bar-tab-post-open-functions need to be called during tab-bar
> initialization. Currently, a user's custom post-open functions are invoked
> only for tabs created beyond the initial tab. This is a bug, in my view.

Please explain what are you trying to achieve?

'tab-bar-tab-post-open-functions' is intended to be run in a new tab
explicitly created by the user via 'tab-bar-new-tab-to'.

OTOH, 'tab-bar-tabs' is a function that returns a list of existing tabs.