Just my 2 cents.
There is a post on vim-use that may (or not) interest pida dev ...
It's about vim api and the fact that vim doesn't have a clean
seperation between the actual
data handling, command parsing and execution etc and the visual
Look at the end of the post here:
Have a nice day
On 13 sep, 18:35, Francois <[EMAIL PROTECTED]> wrote:
> Thanks guys for your answers
> I'm happy to see that Pida is healthy and in very good shape
> Best wishes
> On 13 sep, 05:22, "Ali Afshar" <[EMAIL PROTECTED]> wrote:
> > 2008/9/12 RonnyPfannschmidt <[EMAIL PROTECTED]>:
> > > On 12 Sep., 19:23, Francois <[EMAIL PROTECTED]> wrote:
> > >> What do you mean by a rich vim api (vim is my editor of choice with
> > >> pida) ?
> > > the current vim api is based on vims remote protocol
> > > its VERY limited
> > Well, it's certainly not "very limited", it has complete control over
> > anything Vim can do. But there are a couple of small issues that
> > prevent us from reaching absolute perfection with it, and hence:
> > > ali is experimenting with the integration of dbus/grpc for better apis
> > dbus/grpc are just ways to communicate with Vim (and we could
> > essentially plug anything in there), it's the actual Vim API that is a
> > bit painful. I am suspecting that the complete solution is a
> > combination of the real Vim API, augmented with some vim-python over
> > dbus/grpc.
You received this message because you are subscribed to the Google Groups
To post to this group, send email to firstname.lastname@example.org
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at