We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
mate-settings-daemon $ grep mateconftool-2 data/org.mate.keybindings.gschema.xml.in <default>'mateconftool-2 --toggle /desktop/mate/applications/at/screen_magnifier_enabled'</default> <default>'mateconftool-2 --toggle /desktop/mate/applications/at/screen_reader_enabled'</default> <default>'mateconftool-2 --toggle /desktop/mate/applications/at/screen_keyboard_enabled'</default>
<default>'mateconftool-2 --toggle /desktop/mate/applications/at/screen_magnifier_enabled'</default>
<default>'mateconftool-2 --toggle /desktop/mate/applications/at/screen_reader_enabled'</default>
<default>'mateconftool-2 --toggle /desktop/mate/applications/at/screen_keyboard_enabled'</default>
The text was updated successfully, but these errors were encountered:
There is no --toggle equivalent in gsettings/dconf
Sorry, something went wrong.
I have 2 solutions to this:
bash script: http://paste.mate-desktop.org/view/07def43d Python script: http://paste.mate-desktop.org/view/7193d8b6
Personally I like the python version but I know @stefano-k wants the bash version. Can you test the bash version and let me know if this works?
Update schema to use toggle shell script
efab79f
Fixes #32
48aa831
No branches or pull requests
mate-settings-daemon $ grep mateconftool-2 data/org.mate.keybindings.gschema.xml.in
<default>'mateconftool-2 --toggle /desktop/mate/applications/at/screen_magnifier_enabled'</default>
<default>'mateconftool-2 --toggle /desktop/mate/applications/at/screen_reader_enabled'</default>
<default>'mateconftool-2 --toggle /desktop/mate/applications/at/screen_keyboard_enabled'</default>
The text was updated successfully, but these errors were encountered: