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
Hide / Compact UI at runtime #1400
Comments
This seems to be a duplicate of #694. |
True. It was a little hard for me to find the other one because its title talks about the implementation rather than the user feature. This one is in the roadmap SVG though (which is not super trivial to change) - is it ok if we leave it open and close both once this is implemented? |
Sure, it is OK. I just want to make it obvious to connect all the information. |
This would also be very helpful when doing screencasts/live streams. I’d love to be able to hide the interface after performing an action so I have as much screen space as available given how small the available space is when you’re presenting on 1080p with large fonts, etc. :) |
Hey @aral - while I very much agree, I just want to make sure you know about |
While I also like the idea of being able to switch, these days I rarely start zellij in the default layout, since I'm quiet familiar with the key bindings now. But still especially for new people it could be a helpful feature. |
Not sure if this is the right place, but in compact mode, when a pane is full-screened, I frequently find myself forgetting if I have other panes (on this tab) or not. i.e. it would be good to have something showing the number of panes in the tab, or an F or something to indicate I'm in full screen mode. The presence of floating windows could also be useful. e.g. current:
idea:
|
Hey @artfulrobot - all of this is possible to achieve with plugins. |
Plugins / Layouts in general and the Zellij UI specifically should support a compact mode and a "hidden ui" mode.
The compact UI should include one bar with a list of open tabs and the current mode.
Depends on: #742
The text was updated successfully, but these errors were encountered: