I understood the use case and of course, if the menubar is hidden once, it should be hidden again after restart. What I meant is that we just need to store the state (visible or hidden) and restore that state on startup. If we would implement it like the other interface component toggles (Sidebar, Toolbar, ...), it would be as easy as just a couple of copy&paste's and for the user it would be a consistent experience to show/hide various parts of the interface.

Agree with @eht16, see #2972 (comment)

And more users can use this at all as a menu item in the View menu and an option in the preferences dialog is easier to discover than a keybinding.

Agreed, I have been assuming mnemonics work even if the menu is hidden, @xiota could you check?

If they do then having a menu item means there is a fixed activation that can be documented. If the only way to make the menubar visible is a user settable keybinding then it can't be documented because nobody knows what the user set it to.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.