Editing DbusScripts
Warning: You are not logged in.
Your IP address will be recorded in this page's edit history.
Warning: This page is 38 kilobytes long; some browsers may have problems editing pages approaching or longer than 32kb. Please consider breaking the page into smaller sections.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 110: | Line 110: | ||
==== The incredibly useful --debug flag ==== | ==== The incredibly useful --debug flag ==== | ||
- | The --debug flag is essential for looking at what's going on if you plan to write your own scripts. Run "dbus-scripts --debug" in a terminal and then perform whatever actions on the phone, to see all the events you can process using dbus-scripts. To see events on the session bus, make that "dbus-scripts --debug --session" (but you will need to run it through | + | The --debug flag is essential for looking at what's going on if you plan to write your own scripts. Run "dbus-scripts --debug" in a terminal and then perform whatever actions on the phone, to see all the events you can process using dbus-scripts. To see events on the session bus, make that "dbus-scripts --debug --session" (but you will need to run it through run-standalone.sh). |
- | < | + | ie |
+ | <source lang=text> | ||
sudo dbus-scripts --debug | sudo dbus-scripts --debug | ||
sudo /usr/bin/run-standalone.sh dbus-scripts --debug --session | sudo /usr/bin/run-standalone.sh dbus-scripts --debug --session | ||
- | </ | + | </source> |
== Usage, tips and tricks == | == Usage, tips and tricks == |
Learn more about Contributing to the wiki.