Hi, On 03.07.2013 16:16, Jean-Sébastien Pédron wrote: > This allows one to run multiple awesome instances on the same machine > and still be able to target one specific instance using > awesome-client(1). > > Because some characters are forbidden in a bus name, characters not > matching [A-Za-z0-9_-] are replaced by '_'. > > When $DISPLAY is not set, ":0.0" is assumed. Also, when $DISPLAY doesn't > specify the screen number (eg. ":1"), ".0" is appended to normalize the > bus name (eg. ":1" becomes ":1.0"). > > The bus name is computed in a_dbus_init() (in dbus.c) and is exposed > through the dbus.bus_name variable to Lua. > > Note that when using a remote display, the bus name will contain the > X server host name. In this case, awesome-client(1) will be able to > target awesome only if both run on the same host (ie. are attached to > the same D-Bus). Otherwise, awesome-client(1) will do nothing. Before > this patch, awesome-client(1) could target the local awesome instance > instead. > > Example: > Previous bus name: org.naquadah.awesome.awful > New bus name: org.naquadah.awesome.awful._0_0 (for DISPLAY=:0.0) > ---
I don't have much clue about dbus, but I don't think I ever saw anything else doing something like this. This seems like a hint that this isn't the correct solution for this (also, it pretty much defeats the point of well-known bus names). Did you see this approach suggested somewhere or did you just come up with it? Uli -- Bitte nicht mit dem verbleibenden Auge in den Laser gucken. - Vincent Ebert -- To unsubscribe, send mail to [email protected].
