Editing Desktop Command Execution Widget scripts
Warning: You are not logged in.
Your IP address will be recorded in this page's edit history.
Warning: This page is 35 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 8: | Line 8: | ||
===Scripts without output=== | ===Scripts without output=== | ||
- | When there's no output (for example if you're using widget as a button and you use D-Bus call) the widget displays "Invalid Command". This can be most easily avoided if you pipe echo "" at the end of the command. This is | + | When there's no output (for example if you're using widget as a button and you use D-Bus call) the widget displays "Invalid Command". This can be most easily avoided if you pipe echo "" at the end of the command. This is alo usable if your script produces unwandet output (D-Bus reply for example). |
dbus-send -options -moreoptions | echo "" | dbus-send -options -moreoptions | echo "" | ||
Collection of D-Bus calls can be found on [[Phone control]] wiki page. The basic principle for making a script for DCEW is the same as above (D-Bus command and piping an echo). | Collection of D-Bus calls can be found on [[Phone control]] wiki page. The basic principle for making a script for DCEW is the same as above (D-Bus command and piping an echo). | ||
+ | |||
===Scripts with long output=== | ===Scripts with long output=== |
Learn more about Contributing to the wiki.