Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Actualvim – Sublime Text 3 input mode powered by Vim itself

github.com

Post reply on HN
Print view View original

101–110 of 112 posts

Re: Actualvim – Sublime Text 3 input mode powered by Vim itself

#101

Post by lunixbochs »

justinmk wrote: post #100
lunixbochs wrote: post #81

Earlier quoted context omitted.

Isn't eclim primarily to use Vim as the frontend and Eclipse as the backend? Same idea, slightly different scenario. I used it for linting Java over in sublimelint. I developed ActualVim using only a VT100 reference ( http://bochs.info/text/vt100.txt ) and `:help netbeans`

The core of eclim is a server that talks to the Eclipse JDK, for which there are vim, emacs, etc, front-ends. Eclim also happens to provide an Eclipse plugin that _embeds_ Vim in Eclipse, using the NetBeans protocol, just as you are embedding Vim in Sublime. The author of eclim is also very responsive, if you wanted to ask him about anything.

Is he not just embedding a VT100 emulator and using NetBeans socket to copy the buffer back and forth? The primary focus of NetBeans integration is to pass basic state forth and not to facilitate a full Vim embed.

Re: Actualvim – Sublime Text 3 input mode powered by Vim itself

#103

Post by justinmk »

lunixbochs wrote: post #101
justinmk wrote: post #100

Earlier quoted context omitted.

The core of eclim is a server that talks to the Eclipse JDK, for which there are vim, emacs, etc, front-ends. Eclim also happens to provide an Eclipse plugin that _embeds_ Vim in Eclipse, using the NetBeans protocol, just as you are embedding Vim in Sublime. The author of eclim is also very responsive, if you wanted to ask him about anything.

Is he not just embedding a VT100 emulator and using NetBeans socket to copy the buffer back and forth? The primary focus of NetBeans integration is to pass basic state forth and not to facilitate a full Vim embed.

To be honest, I don't know. An eclim discussion[1] implies that eclim is using Vim's NetBeans protocol, and the eclim code that I have read is well-organized and the project is mature, so when you said you were having issues with the NetBeans protocol I thought eclim might be a useful reference for you.

[1] https://github.com/ervandew/eclim/issues/100

Re: Actualvim – Sublime Text 3 input mode powered by Vim itself

#104

Post by lunixbochs »

justinmk wrote: post #103
lunixbochs wrote: post #101

Earlier quoted context omitted.

Is he not just embedding a VT100 emulator and using NetBeans socket to copy the buffer back and forth? The primary focus of NetBeans integration is to pass basic state forth and not to facilitate a full Vim embed.

To be honest, I don't know. An eclim discussion[1] implies that eclim is using Vim's NetBeans protocol, and the eclim code that I have read is well-organized and the project is mature, so when you said you were having issues with the NetBeans protocol I thought eclim might be a useful reference for you. [1] https://github.com/ervandew/eclim/issues/100

Oh, that's awesome. I didn't think of using it like that.

They're using a Vim script to extend the NetBeans protocol and pass arbitrary messages back with nbkey/keyCommand. I can totally use this. Thanks!

Re: Actualvim – Sublime Text 3 input mode powered by Vim itself

#105

Post by chrisbra10 »

leokun wrote: post #40
m2mdas wrote: post #38

Earlier quoted context omitted.

WTF are you talking about? Vim have may have many demerits but segfaults is not on that list. If segfaults are that frequent you described then people would have jumped ship already. I can't comment on the code structure of Vim but it does not matter to me because end product is working fine for me for 5+ years. Also bad code structure did not stop continuous development of Vim. Just for example there were 1000 patch…

Nope, and nope. > WTF are you talking about? Vim have may have many demerits but segfaults is not on that list. If segfaults are that frequent you described then people would have jumped ship already. Vim is all segfaults once you introduce async, and it's highly unstable during any dev work. On any given day visit the Vim dev mailing list and scroll down. Today I see: Scrolling in a c file segfaults: https://groups.…

Bram usually takes segfauls very seriously and usually fixes them very fast: > Scrolling in a c file segfaults: https://groups.google.com/forum/#!topic/vim_dev/teRV3RyDtzc Obviously not a Vim problem, as has been mentionend in the linked thread.

>Referencing an old buffer seg faults: https://groups.google.com/forum/#!topic/vim_dev/Mssm8pKtnGM Fixed with 7.4.59. It is pretty clear, this is a problem, but I wonder how to reproduce it, because I have never seen it crash there when closing buffers. So there must be some additional step to trigger it, otherwise we would have seen a lot more segfaults.

> Segfault opening a readme: https://groups.google.com/forum/#!topic/vim_dev/SE31YUccJN4

probably caused by the new regexp-engine, that was introduced with 7.4 I am not entirely happy about including it and there seem to be still several bugs in it, but it is not even clear, if that crash has not already been fixed.

> Segfault selecting a lot of text: https://groups.google.com/forum/#!topic/vim_dev/yzVqZ3qogho A recurring issue, that seems to happen to me too once in a while. Nobody knows what the cause is so, it can't be fixed currently. Seem to be not a problem of Vim, but of some of the X libraries.

> Segfault on autocompletion: https://groups.google.com/forum/#!topic/vim_dev/lqcn57eRGGs might have already been fixed. The reporter does not mentioned, how to reproduce it or even what version he uses.

> Segfault on tab switching: https://groups.google.com/forum/#!topic/vim_dev/Vc9Z8rfe22w Not exactly sure, what causes this.

> Just keep scrolling, the segfaults never stop. It's not as bad as you make it sound. Usually segfaults are taken seriously by Bram and will be fixed soon, if the problem is clear. Second, even in your list, you needed to scroll back a couple of months. I wouldn't call that exactly an evidence, that Vim is full of segfaults.

Even though the code is a mess, full of nested ifdefs and uses a lot of global state variables, I have not often seen segfaults and I have been providing many patches in the last years and there are still many patches of mine in the todo list. Overall I am quite happy, with a Vi clone that is actively maintained and even further developed, although sometimes I wish for some more activities in fixing bugs and adding features. But Bram seems to be too busy to take a more active role.

Re: Actualvim – Sublime Text 3 input mode powered by Vim itself

#106

Post by chrisbra10 »

leokun wrote: post #25
tmhedberg wrote: post #20

Earlier quoted context omitted.

A patch series implementing asynchronous timers has in fact recently been posted to the Vim development list [^1]. Its status is uncertain, and is still being actively discussed, but to state that such a thing "will never be possible" is just blatantly false. [^1]: https://groups.google.com/forum/#!topic/vim_dev/-4pqDJfHCsM%...

Actually I know all about that patch and have commented in that thread. I tried that patch and vim segfaults. It's not the patch's fault, it's vim's fault. Checkout this response from Bram when one of the devs for that patch reveals an error: https://groups.google.com/forum/#!searchin/vim_dev/kans/vim_... It's clearly an unsafe operation that wont work with async/timed code, because the buffer may be null at that poi…

> https://groups.google.com/forum/#!searchin/vim_dev/kans/vim_....

[...]

This has been acknowledged and even patched as you surely know. So what are you complaining about exactly?

Re: Actualvim – Sublime Text 3 input mode powered by Vim itself

#107

Post by chrisbra10 »

leokun wrote: post #42
duaneb wrote: post #39

Earlier quoted context omitted.

I have no idea how you make vim crash; usually it's because I attempt to search through a multigigabyte file or something. Vim may have many issues but stability is NOT one of them.

You are quite wrong, on any given day vim dev's mailing list has recent seg faults at the top of its list.

It is not as bad as you make it sound. We are currently seeing many segfaults because of the release of 7.4 and its inclusion of a new regexp engine. Other then that, there are not more segfaults then usually, which is not that bad.

Re: Actualvim – Sublime Text 3 input mode powered by Vim itself

#108

Post by lunixbochs »

justinmk wrote: post #103
lunixbochs wrote: post #101

Earlier quoted context omitted.

Is he not just embedding a VT100 emulator and using NetBeans socket to copy the buffer back and forth? The primary focus of NetBeans integration is to pass basic state forth and not to facilitate a full Vim embed.

To be honest, I don't know. An eclim discussion[1] implies that eclim is using Vim's NetBeans protocol, and the eclim code that I have read is well-organized and the project is mature, so when you said you were having issues with the NetBeans protocol I thought eclim might be a useful reference for you. [1] https://github.com/ervandew/eclim/issues/100

The picture on this page answers my question: http://eclim.org/

VT100 embed is their third mode.

Re: Actualvim – Sublime Text 3 input mode powered by Vim itself

#109

Post by leokun »

chrisbra10 wrote: post #106
leokun wrote: post #25

Earlier quoted context omitted.

Actually I know all about that patch and have commented in that thread. I tried that patch and vim segfaults. It's not the patch's fault, it's vim's fault. Checkout this response from Bram when one of the devs for that patch reveals an error: https://groups.google.com/forum/#!searchin/vim_dev/kans/vim_... It's clearly an unsafe operation that wont work with async/timed code, because the buffer may be null at that poi…

> https://groups.google.com/forum/#!searchin/vim_dev/kans/vim_... . [...] This has been acknowledged and even patched as you surely know. So what are you complaining about exactly?

I didn't know it was patched.

https://groups.google.com/forum/#!searchin/vim_dev/set_last_...

Cool.

Re: Actualvim – Sublime Text 3 input mode powered by Vim itself

#110

Post by justinmk »

lunixbochs wrote: post #104
justinmk wrote: post #103

Earlier quoted context omitted.

To be honest, I don't know. An eclim discussion[1] implies that eclim is using Vim's NetBeans protocol, and the eclim code that I have read is well-organized and the project is mature, so when you said you were having issues with the NetBeans protocol I thought eclim might be a useful reference for you. [1] https://github.com/ervandew/eclim/issues/100

Oh, that's awesome. I didn't think of using it like that. They're using a Vim script to extend the NetBeans protocol and pass arbitrary messages back with nbkey/keyCommand. I can totally use this. Thanks!

Very interesting. Thanks for relaying that.
Post reply on HN