Skip to content

The tab-group number counts the tabs in one folder, not all of them - #197

Open
astetic-dev wants to merge 1 commit into
mainfrom
fix/196-tab-group-per-folder
Open

The tab-group number counts the tabs in one folder, not all of them#197
astetic-dev wants to merge 1 commit into
mainfrom
fix/196-tab-group-per-folder

Conversation

@astetic-dev

Copy link
Copy Markdown
Owner

Fixes #196.

Set to 4, the number bundled a folder that held two tabs: it gated whether grouping happened (over all tabs together) while the group size itself was hard-coded at two. The label promises the folder, so that is what the number now means.

  • A folder collapses into one tab as soon as it holds that many sessions; folders below it keep their own tabs, each in its own place in the bar.
  • The total-tab gate is gone. Grouping only ever merges sessions that share a folder, so ten agents in ten folders were never helped by it anyway.
  • tabGroupAt -> tabGroupSize, default 3. A stored number other than the old default 10 carries over unchanged; 10 (the old default) becomes the new default instead of a silently dead setting.
  • 0 still means never; 1 is read as 2, because a group of one is not a group.
  • Labels and help in nl + en now say "tabs in that folder", and mention 0 = never.

Checked by running the real tabRows() source against the reporter's own session list (nine sessions, two sharing a folder, setting 4): nine ordinary tabs, no session dropped from the bar. Same for size 4 with a four-session folder, size 2, size 1, and grouping off.

Setting it to 4 bundled a folder that held two tabs, because the number gated
whether grouping happened at all while the group size itself was hard-coded at
two. The label promises the folder, so that is what the number now means: a
folder collapses into one tab as soon as it holds that many sessions, and
folders below it keep their own tabs, each in its own place in the bar.

The total-tab gate goes with it. It bought little -- grouping only ever merges
sessions that share a folder, so the crowding of ten agents in ten folders was
never helped by it.

tabGroupAt becomes tabGroupSize (default 3). A stored number other than the old
default moves over unchanged: whoever typed one meant the folder.

Fixes #196
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

The tab-group number counts all tabs, not the tabs in one folder

1 participant