mb-applet-launcher -V (return code: 1)
Cannot open display:
Usage mb-applet-launcher [Options..] <png|xpm> <app>
Where options are:
-display, -d <display> X11 display to connect to.
--title, -n <title> Set panel's title.
--no-animation,-na Disable animations, if relevant.
. --start, -s Start app instance immediately.
The default action is to (un)iconize selected app. Alternate actions:
--kill, -k Destroy app.
--respawn, -l Respawn multiple instances.
--message, -m Pipe app's stdout to the panel as a message.
Alternatively just a valid .desktop file can be given:
mb-applet-launcher --desktop <.desktop file>
However with this option -k,-l and -m will have no effect.
The presence of a SingleInstance=True key/pair in the .desktop file
will achieve similar functionality.
mb-applet-launcher --help (return code: 1)
Cannot open display:
Usage mb-applet-launcher [Options..] <png|xpm> <app>
Where options are:
-display, -d <display> X11 display to connect to.
--title, -n <title> Set panel's title.
--no-animation,-na Disable animations, if relevant.
. --start, -s Start app instance immediately.
The default action is to (un)iconize selected app. Alternate actions:
--kill, -k Destroy app.
--respawn, -l Respawn multiple instances.
--message, -m Pipe app's stdout to the panel as a message.
Alternatively just a valid .desktop file can be given:
mb-applet-launcher --desktop <.desktop file>
However with this option -k,-l and -m will have no effect.
The presence of a SingleInstance=True key/pair in the .desktop file
will achieve similar functionality.