I read here that the community decided over three years ago on restricting the subject-mater material. There were no dissenting views. Moreover, the Area51 discussions also lack any dissenting views from the now dominant opinion. The FAQ has only this to say,
Please limit your questions to specific queries about members of the Vi and Vim family of editors
To summarize, most of these discussions have assumed a definition of "vim ecosystem" as being,
- A text-editor
- That descends from vi/vim.
For me, that's a very narrow definition.
My perspective
As a thought experiment,
- If some of the code was borrowed directly from Vim and integrated into the browser, would the browser then be on topic here?
- If Vim was directly compiled to Web Assembly and you ran it on a web page would it be on topic here?
- If Vim was re-implemented in JavaScript with the intention to be full-featured implementation, would it be on topic here?
- If something targets vim users, and is made possible only through extension should it be on topic here like VRoom, Vimium, or Surfing Keys?
I don't just use VI, I use other utilities that focus primarily on VIM-keybindings, and I'm interested in spreading these keybindings and this object-modifier syntax to other aspects of the computer-interface. I believe that Vim creates people like me, and the popularity of these tools speaks to that. I think this site would be better if it made an effort to cater to #VimLife or whatever, and not just the editor.
Suggested Fix
If you ask me what makes Vi and Vim unique and a better method to establish subject matter boundary for the site, I would prefer to differentiate on,
- Software created for the goal of Vi-like keybindings.
- A difference between insert and non-insert (edit/browse/navigate etc) mode.
While of course leaving all the things currently on-topic, on-topic.
Implications
This would immediate make the following types of software on topic,
- CVim, and Surfing Keys
- IdeaVim: Moded VIM editing for the JetBrains IDE
- Readline's VI Mode
- Moded Plugins for IDEs that emulate vim keybindings.
hjkl
to navigate in a web page or to control your browser doesn't have anything to do with Vim. It is not about manipulating text, it is not about integrating your text editor with external tools and (IMO) it is not even about making your browser a modal tool since the navigation in the browser is completely decorrelated to the (few) times you need to insert text.:tabn
doesn't exist": off topic, "How do I create a mapping to open a new browser tab in CVim": off topichjlk
pages the screen like in vim, but there are probably hundreds of keybindings including an analog[g]go
,[y]ank
,[m]ark
,[p]aste
. And if you hit any text box and typeCtrl+i
, as compared to regular insert mode, you get a JavaScript VIM box popup at you so you can edit it with ACE in vim mode. Surfing Keys has ~8k users. cVim has ~40,000 users. My assumption is many of them are on this site; my belief, that it would enhance the community for all if those were welcomed contributions.go
ing to somewhere is not common to navigating a code base in Vim or even any file. Yanking and pasting don't have the same purpose in a browser (getting some text to use in another software or filling a form) than in a text editor (most of the time, moving some code around). The Vim pop up could fall into the "editor behaving like Vim" scenario. For your assumption about the communities overlaps I would be curious to see some numbers about that and I still think that merging two community because they use unrelated tools is not the best idea.