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
This is a feature of Terminal.app that seems worthwhile to add, both as a binding action and as a menu action to mimic Terminal.app. The default binding of option+command+O can also be copied from Terminal.app.
Since this is a binary toggle and macos-option-as-alt is not a binary configuration, I believe the behavior of the action should be as follows:
Default the toggle to the value of the configuration. If macos-option-as-alt is true, it should show up checked.
When untoggled, the value goes to false.
When retoggled, the value returns back to the configured truthy value (if set) or true otherwise. This behavior lets the "on" behavior match what the user desired by default (left/right/true).
We should be clear in the documentation for the binding action how this behaves.
The discussion also noted a UI indication when this turns on and off. If we can get that in, that's great, but if not we can defer that to future work.
The text was updated successfully, but these errors were encountered:
As discussed here: #2517
This is a feature of Terminal.app that seems worthwhile to add, both as a binding action and as a menu action to mimic Terminal.app. The default binding of option+command+O can also be copied from Terminal.app.
Since this is a binary toggle and
macos-option-as-alt
is not a binary configuration, I believe the behavior of the action should be as follows:macos-option-as-alt
is true, it should show up checked.false
.true
otherwise. This behavior lets the "on" behavior match what the user desired by default (left/right/true).We should be clear in the documentation for the binding action how this behaves.
The discussion also noted a UI indication when this turns on and off. If we can get that in, that's great, but if not we can defer that to future work.
The text was updated successfully, but these errors were encountered: