Le Mon, 19 May 2008 14:54:32 +0200, "Yakov Lerner" <[EMAIL PROTECTED]> a écrit :
> On Sat, May 17, 2008 at 4:45 PM, Alban Crequy > <[EMAIL PROTECTED]> wrote: > > > > > The D-Bus connection is an Unix socket. When vim fires a signal > > from the > > > > Does it require a daemon or something ? Although two process can communicate using the D-Bus protocol without a daemon, the usual way to do it on the desktop is through dbus-daemon with an Unix socket. Using TCP from a remote host is possible too, but that's not what I wanted to do. Application using D-Bus can use libdbus as a build dependency. > That is a burden of additional dependency > that I would not like, personally. Do you mean it should be optional at compilation time with a flag, or do you mean you would like to have the feature without any additional dependency? > Why not use vim-remote mechanism ? > It is event-driven and already built into vim. I didn't looked at the vim-remote mechanism yet. But I fear the protocol is tied to vim. My goal was to have a common protocol used by several editors (like gedit, kate, vim, emacs). > If you want to artificially limit your mechanism it to be host-local I don't want the mechanism to be limited to the local host, but I don't want to put the network code in the editor. I would prefer to reuse the network code that handles TCP, XMPP or another backend in other editors too. editor <--(D-Bus)--> unnamed software <--(internet)--> ... my contact where the connection on Internet can be TCP or a Telepathy tube. > and then there are more portable solutions than d-bus > (windows has no d-bus). Windows has winDBus but I never tried it: http://sourceforge.net/projects/windbus Telepathy has D-Bus tubes to allow applications to use D-Bus on Jabber (i.e. not on the same host). OLPC use D-Bus tubes, so an activity can communicate between your laptop and your contacts' laptops through Jabber (in this case, dbus-daemon is not used). -- Alban --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
