You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be useful to maximize mate-terminal when it is opened regardless method (for example, from mate-panel --run-dialog).
For comparison, this will always maximize the window in caja: gsettings set org.mate.caja.window-state maximized true
Actual behaviour
There's no setting to mate-terminal always maximize the window
Steps to reproduce the behaviour
This setting will maximize the window with the keyboard shortcuts: gsettings set org.mate.applications-terminal exec 'mate-terminal --window --maximize'
However, the above setting is only maximizing the window from keyboard shortcut, usually controlled by Ctrl+Alt+t, see: gsettings get org.mate.Marco.global-keybindings run-command-terminal
MATE general version
1.26.0
Package version
1.26.0
Linux Distribution
Ubuntu MATE 22.04
Link to bugreport of your Distribution (requirement)
Feature request
The text was updated successfully, but these errors were encountered:
Expected behaviour
It would be useful to maximize mate-terminal when it is opened regardless method (for example, from
mate-panel --run-dialog
).For comparison, this will always maximize the window in caja:
gsettings set org.mate.caja.window-state maximized true
Actual behaviour
There's no setting to mate-terminal always maximize the window
Steps to reproduce the behaviour
This setting will maximize the window with the keyboard shortcuts:
gsettings set org.mate.applications-terminal exec 'mate-terminal --window --maximize'
However, the above setting is only maximizing the window from keyboard shortcut, usually controlled by Ctrl+Alt+t, see:
gsettings get org.mate.Marco.global-keybindings run-command-terminal
MATE general version
1.26.0
Package version
1.26.0
Linux Distribution
Ubuntu MATE 22.04
Link to bugreport of your Distribution (requirement)
Feature request
The text was updated successfully, but these errors were encountered: