Vim 8.2 Released With Support For Popup Windows

[phoronix]

Phoronix: Vim 8.2 Released With Support For Popup Windows

For those preferring the Vim text editor, Vim 8.2 is out today and its primary new feature is support for "popup windows" and for demonstrating those new capabilities is even a new Vim-based game called Killer Sheep...

http://www.phoronix.com/scan.php?page=news_item&px=Vim-8.2-Released

[Candy]

VIM is EMACS done right! Praise VIM!

[CommunityMember]

KillerSheep is a baaaaaad baaaaaad game... (someone had to say it)

[timofonic]

Now VIM needs a window manager and a compositor for it. VimOS FTW!!!!!1111

Jokes aside: Does this mode also has a graphics mode?

PS: What about NeoVIM? It had popup windows ages ago. It even has has floating windows, multigrid and others.

[maarten]

Does this mean that vim will also need a pop up blocker?

[timofonic]

Does this mean that vim will also need a pop up blocker?

Rewriting uBlock in VimL would be a huge PITA.

[ssokolow]

VIM is EMACS done right! Praise VIM!

As a Vim user, I have to say that they both have deep design flaws that can't be fixed without major breakages to their existing ecosystems. In Vim's case, it's mainly that its extensibility grew organically, which is why plugin composition is so fragile.

[Candy]

I have to say that they both have deep design flaws that can't be fixed without major breakages to their existing ecosystems.

... and ? I use it as an Editor not as an Operating System. VIM served me well for many many years now.

[ssokolow]

... and ? I use it as an Editor not as an Operating System. VIM served me well for many many years now.

Vim has served me well for ages too, but it does mean that I'm still tracking down and reporting bugs caused by the switch to async plugins I did a few months ago.

(At the moment, I'm trying to find time to diagnose why, in certain context, ALE fights to keep my pointer from appearing to move when I hold down an arrow key because I'm blanking on a more precise motion.)

If it had a more solid model for plugin interaction, rather than just expecting plugins to spend half their time faking user input, these bugs wouldn't happen.

(It reminds me of how I had to completely rewrite some code from a blog post detailing how to implement spell-checking in PyQt text-entry widgets because the guy who wrote it didn't seem to understand how to create secondary cursors rather than manipulating the visible one.)

[Candy]

If it had a more solid model for plugin interaction, rather than just expecting plugins to spend half their time faking user input, these bugs wouldn't happen.

I do understand this. But please bear in mind, that VIM has been released around 1991. Probably as a hobbiest project by someone, who started this out of fun. During that time (this also includes me and my own programming history), a project started with few basic functions and evolved into something that we know as what VIM is today. I do believe you, that there is a lot of potential for improvements. But at the end of the day... It's still an editor... The most popular as we speak...