-
-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ability to use native tabs on macOS #2946
Comments
I'm afraid I have no interest in implementing OS native tabs. Note that |
Hi, totally understand not wanting to implement native tabs (as kitty is cross-platform I imagine you want to keep any platform-specific code to a minimum). What I'm really saying is that it seems the behavior I want is already there - i.e. whatever macOS is doing when you make a new window in fullscreen, I just want that. No special other behavior is needed! I'm just looking for a way to get the thing that's already happening, but not only in fullscreen :-) Note that most macOS apps do not have this behavior (creating a new window in fullscreen mode creates a new fullscreen window in a different space, not a native tab), so there's something kitty is already doing to make new windows in fullscreen create tabs rather than a new window. Not being a mac programmer I'm not really sure what it is, but I could try to investigate that if it would help (and if you'd in principle be open to it?) I can't tell if you are just saying "this seems like not a good use of my time" or "I'm philosophically opposed to it being in kitty". Also thank you so much for making kitty, it's really fantastic. |
No, I'm afraid there really isnt anything kitty is doing, other than |
I just ran across this thread looking for exactly the same thing...too bad it won't be implemented. That is a feature I use heavily in iTerm. |
@agnoster I've just tried what you suggested
But when I do so, the newly opened window doesn't open in a native tab but in a new window in it's own space. When I leave fullscreen in the newly created window, the old one stays in its own space, still in fullscreen and then I have 2 distinct windows. I know the workaround you gave is almost 3 years old so maybe it simply doesn't work anymore, but any help would be appreciated. |
I also wish we had native Mac OS tabs 😞. Personally, my preference is for a great terminal that feels both fast and native, I can compromise on the native part for the fast part. But I'm more inclined to jump ship when a new term appears that matches kitty performance and is also native. Some food for thought in terms of how the project fits into the ecosystem... |
Is your feature request related to a problem? Please describe.
This is perhaps purely a visual preference, but I prefer the "chrome" of my terminal to be visually distinct from the "content" of the terminal, and have a strong preference for native-style tabs over the rendered-in-terminal tabs that are the kitty standard.
Describe the solution you'd like
Any solution - even if it requires some workarounds - would be helpful to me. For example:
Describe alternatives you've considered
I already often use kitty in fullscreen mode just to get this behavior - when you open a new window in fullscreen, kitty creates an os-native tab instead. I love this, and so I already sometimes just fullscreen+new window+un-fullscreen, but I think we can all agree that's cumbersome (I often create and destroy tabs dozens of times in a day). The fact that kitty already supports this tab style makes me hopeful that it could in theory be supported. These native tabs seem to support a lot of functionality - you can even drag and drop native tabs to reorder or even between windows! So they already exist and work great - why can't I find a keybinding to create them out of fullscreen mode?
Additional context
Add any other context or screenshots about the feature request here.
Example of the current normal "terminal tabs":
Example of creating new windows in fullscreen and switching back to get "native tabs":
The text was updated successfully, but these errors were encountered: