Skip to content
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

specify to start in fullscreen from session file? #5863

Closed
rionda opened this issue Jan 6, 2023 · 3 comments · Fixed by #6035
Closed

specify to start in fullscreen from session file? #5863

rionda opened this issue Jan 6, 2023 · 3 comments · Fixed by #6035
Labels

Comments

@rionda
Copy link

rionda commented Jan 6, 2023

This is a question: is there a way to specify in a session file that the OS window should be fullscreen?

I tried with toggle_fullscreen and startaas fullscreen, but it gives me errors.

More generally, it is unclear to me what commands can go in a session file (e.g., the docs use focus_os_window which is not documented anywhere).

@rionda rionda added the bug label Jan 6, 2023
@kovidgoyal
Copy link
Owner

Nope. Every command that can go in a session file is documented at https://sw.kovidgoyal.net/kitty/overview/#startup-sessions

@ad-chaos
Copy link
Contributor

ad-chaos commented Jan 6, 2023

In that case, would you mind changing

kitty/docs/overview.rst

Lines 127 to 130 in 397ac36

You can control the :term:`tabs <tab>`, :term:`kitty window <window>` layout,
working directory, startup programs, etc. by creating a *session* file and using
the :option:`kitty --session` command line flag or the :opt:`startup_session`
option in :file:`kitty.conf`. For example:

to say something like the following, or something similar to it?

You can control the :term:`tabs <tab>`, :term:`kitty window <window>` layout,
working directory, startup programs, etc. by creating a *session* file and using
the :option:`kitty --session` command line flag or the :opt:`startup_session`
option in :file:`kitty.conf`. An example utilising all the options:

@rionda
Copy link
Author

rionda commented Jan 6, 2023

That seems a good idea. I would suggest: instead of "all the options", say "all the commands that can be used in a session file, including some specific only to such files".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
3 participants