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 ? That is a burden of additional
dependency
that I would not like, personally. Why not use vim-remote mechanism
Hi Alban,
As suggested, you need to look into :help netbeans and at the various
projects that are using the netbeans interface. Don't be mislead by the
name, netbeans interface no longer has anything to do with netbeans.
It's a text protocol over a socket that allows to talk to vim and
Hi Alban,
As suggested, you need to look into :help netbeans and at the various
projects that are using the netbeans interface. Don't be mislead by the
name, netbeans interface no longer has anything to do with netbeans.
Is it still bound to graphical vim (no textmode) ?
Thanks
--
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
Alban Crequy wrote:
My goal was to have a common protocol used by
several editors (like gedit, kate, vim, emacs).
Then I think that you are on the wrong list. You should go to xdg.
Similar things have been done for Audio players, notification system on
the cross desktop lists: having a
Alban Crequy wrote:
I would like to have a support for D-Bus [1] in vim, and then be able
to write vim plug-ins that use the vim D-Bus connection to communicate
with external applications. My goal [2] is to be able to control the vim
buffer from other applications to enable collaboration
On Sat, May 17, 2008 at 4:45 PM, Alban Crequy
[EMAIL PROTECTED] wrote:
...
It seems that this mainloop problem is not specific to D-Bus but other
projects has the same problem:
- Clewn [4]: GDB support in vim. Clewn is an external program but need
a patch in vim to work.
This is not
Hi,
[...]
The D-Bus connection is an Unix socket. When vim fires a signal from the
plug-in, some data is sent through the socket to the dbus-daemon
process. But to receive D-Bus signal, the socket file descriptor must
be added somehow in the vim main loop in order to call a function to
read
Alban,
There is an in-built Netbeans interface in Vim, it works in GVim only.
(See functions netbeans_Xt_connect, netbeans_gtk_connect,
netbeans_w32_connect which set up async socket handler)
I think you could write a bridge between D-Bus and Netbeans interface as
a separate process.
I
