Vim is almost a proper subset of vi, but they're still two different editors, with two different names. Should we create vi and vim?

I am new to using vim. So I think my questions will be in the beginners level only. Should I wait till public beta to ask my questions? Will asking beginner level question impede the site from being launched?

I believe that, these days, most users are using something very close to Bram Moolenaar's Vim, rather than an editor derived from Bill Joy's vi. Furthermore, most of the operations can be done more efficiently in Vim. Should we all just assume that Vim is being used, unless otherwise mentioned?...

To indicate in questions and answers that keystrokes are being typed in normal mode or insert mode, should <kbd> be the convention? Or should we use backticks?

/bin/vi, as written by Bill Joy in the '70's is vi. And /usr/bin/vim, as written by Bram in the '90's, is vim. But we also have nvi (mostly the same), NEO Vim (not even sure what this is), elvis (also a clone with more featues), vile (Emacs like vi, I kid you not), and perhaps a few more. To bo...

Our [help/on-topic] page just contains some generic text. This is probably the most important page in defining the site. Let's collaboratively develop a rough draft as a wiki.

Are installation and associated troubleshooting questions on-topic for this site, or do we want to focus on questions/answers that improve users' actual usage of vi(m) and related software?

There are lots of high-quality vi and vim questions on other Stack Exchange sites; for example, see all the questions tagged vim on SuperUser. Is it possible (and does it make sense) to migrate some of all of these to Vi and Vim?

Lots of very useful vim functionality is available these days through plugins, supported by plugin managers such as Pathogen. I would guess that most experienced vim users use plugins - I certainly do. To what degree are questions about plugins on-topic? Will we indulge a specific question about...

I just opened a question about vimscript. Irrespective of the merits of that particular question, does it make sense to use the vimscript tag? Arguably many/most questions about vim will end up with a small snippet of vimscript, even if it is only a one-liner to be pasted into a ~/.vimrc. When sh...

I think we have some tag confusion that should be resolved as soon as possible. (Maybe I'm just too cautious, but we all know how mass tag edits are bad.) It's programming. From this tag name, it's completely unclear whether it means: Using vi for programming whatever you program. Programming ...

This might be a big issue that we have to resolve before getting out of private/public beta: How programming-related can questions on Vim.SE be? For example, questions about using Vim as a programming tool are probably on-topic. How about programming in Vimscript? What about questions that requi...

The chatroom name is so bland. "Vim." Look at all the creative names others have thought up: "Root Access" for Super User "The DMZ" for Security "The Renderfarm" for Blender "The Litter Box" for Pets "The Hangar" for Aviation "You Are Here" for Travel "The Water Cooler" for The Workplace "The W...

There is a question "What is an effective way to learn vimscript?" on there the following comment received a few upvotes and I think we should clear this on meta: IMHO this question is off-topic because it is too broad, in addition, it's basically asking for "what's the best VimScript tutoria...

Do we want to have tags like x Or possibly group them together, like hkjl, or an aaiioo? (aside: apparently tags are not case sensitive) They could be synonymed to things like delete, movement, or insert-mode respectively. They could also be prefixed with like command-x instead of x.

The title kind of says it all. I'm asking, because this Performing certain operations without clearing the clipboard question seems to be sufficiently answered http://stackoverflow.com/questions/54255/in-vim-is-there-a-way-to-delete-without-putting-text-in-the-register here. Close Downvote Cop...

I wrote a custom syntax highlighting .vim file that doesn't work. Would posting it and explaining what it's supposed to do be on topic? What if I was able to write an MCVE? In either case, would the question be more on topic here, or on SO?

Should questions about how to use vi mode in bash (or readline in general) be on-topic?

Should we have a separate tag for each plugin, instead of a generic plugin tag to cover them all? If so, what should be the naming convention for such tags?

I would like to echo a post that Scott Morrison made on Meta.Tex.SE: I'm a moderator from MathOverflow, and this "question" is actually unsolicited advice, based on our experience from the initial launch of MathOverflow. We should encourage everyone to vote positively as often as po...

Since nobody has the required reputation to suggest tag synonyms yet, please post your tag synonym suggestions below. One suggestion per answer, please. This post will be deleted at the end of private beta. (Hopefully, we can start using the regular tag synonym suggestion mechanism by then.)

To prevent the tagging system from becoming a mess, let's assemble a list of tags that are a bad idea, and what the suggested good alternatives are. One topic per answer, please.

How does one go about creating screencasts, like this one? Should we encourage their use? If so, what minimum standards should there be for the image alt text and accompanying explanation?

How does one go about creating screencasts, like this one? Also see the related question: Should the use of screencasts be encouraged?

Theoretically, vim is supposed to be used to specify that the question is specific to the Vim, that is, Vi IMproved by Bram Moolenaar. However, it appears that this is rarely the case in practice, and I don't think it will be the case in the future either. Almost all questions tagged vim are no...