Feature suggestion: persistent tab numbers, and goto_tab opens new tab mapped to the bind if not already open #3891
Unanswered
stfwn
asked this question in
Ideas and Issue Triage
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hey, thanks for making Ghostty! It's very fast and easy to configure :)
Part 1: persistent tab numbers
My main feature suggestion, inspired by i3, is to have optional persistent tab numbers. This means the tab numbers are not updated after they are opened. E.g.:
Default behaviour:
With this suggested setting:
The new behaviour would be:
Why?
This enables you to build a mental model of where your shell sessions are. For example, you might have a hot reloading debug server process running on tab 3 that you check every once in a while to inspect internal errors while you work on the code in tab 1 and read documentation in tab 2. If you close tab 2, your server process is moved to tab 2, and you'll have a mental cache miss when you next go to tab 3 to inspect it. This takes you out of the flow. With this option enabled, you can open and close any tab, and your server process will always be on tab 3.
Part 2:
goto_tab
opens new tabA natural second feature suggestion following the above, again inspired by i3, is for
goto_tab
to open a new tab mapped to the bind if it is not already open. E.g.:If you only have tab 1 open and you use
cmd+6
, it would open a new tab mapped tocmd+6
. This again enables you to reuse a mental map of where terminals running a certain type of task are. For example, you might always have a terminal running a hot reloading debug server on tab 6, and with this change you can always simply open a terminal at this location and start this process without manually opening the scaffolding tabs 1-5.Beta Was this translation helpful? Give feedback.
All reactions