None of the above.
Write a better answer.
Closing is only for questions that are unanswerable or that are off-topic. The fact that a question has been answered elsewhere is irrelevant.
Lack of research is a valid reason to downvote, but just because the question has been asked somewhere else on the Internet doesn't imply a lack of research. (For one thing,...
I would like to nominate @Carpetsmoker as my first choice for moderator.
His high reputation makes him an obvious candidate, but that's not my only consideration in making this nomination. Not only has he been busy earning points on the main site, he has also been highly active in chat and meta.
I propose a criteria like Carpetsmoker's, but with the last condition modified:
Its main purpose is a text-editor; anything else that has the vi user interface paradigm (so far as one exists) is far too broad a scope.
It must be mostly compatible with the original vi for all basic operations; where mostly is not precisely defined to allow flexibility in ...
Personally, I feel a liberal attitude should prevail; plugins are part of the practical use of vim in this day and age, and I wouldn't want to see too many plugin questions getting closed on that reason alone.
Knows his Vi.
Active on meta
Moderator at codegolf.SE and puzzling.SE
Thanks for the nomination, and I'd be willing to serve as a pro-tem mod for Vi.SE. Not much to say here, but a few points:
I'm glad that you've claimed I'm active on meta, but I haven't been hashing it out here on meta as much as ...
"beginner-level" is not a particularly useful classification here. The criteria you should apply, especially during the private beta, is:
"Does this question require an expert to answer?"
How do you, as a beginner, know whether your question meets that requirement? Simple: do your research!
Have you read a "getting started" ...
For completeness, I'll just reproduce my answer from Area 51…
I, for one, would not like to see hard-core golfing questions where
the shortest keystroke count "wins" the contest.
Golf-lite would be welcome, though. That is, questions should call for
any reasonably efficient technique that one would want to apply
in normal daily use, with some ...
I think that a generic plugin tag is too broad for questions about a specific plugin.
I suggest plugin-fugitive, plugin-nerdtree, etc. Putting "plugin-" as a prefix rather than as a suffix lets them be grouped together in an alphabetical listing.
I'd like to nominate @200_success.
I'm too lazy to go into as much detail as he did in his nomination of @Carpetsmoker, but the effort that he put into that post is actually a great example of why he'd be a good moderator.
I've seen his name popping up all over the main site, and the fact that he actually ...
Disclaimer : I am not a graphist professional, just a guy playing with photoshop and illustrator
Here is an idea :
A simple ascii vim logo, I didn't found any existing version of it yet, so I though it could be a possibility. The font is monaco and the colors are from the solarized theme.
There are (currently) 4 more, you can find them on a GitHub repo I ...
If someone were looking for a way to accomplish something in Vi/Vim, I sure would like them to find this site. These third-party plugins are an integral part of the Vi/Vim experience, so questions about their use should be on topic here.
Stack Exchange works really well for technical support, as long as we're not outsourcing their entire customer support ...
In alphabetical order:
auto_mkdir2.vim by Martin Tournoij from How do I save a file in a directory that does not yet exist? and How can I stop Vim from writing a file without throwing an error?.
colorscheme-changer.vim by Adrien Fabre from How can I set an option differently depending on time of day?.
confirm_quit.vim by Martin Tournoij from How do I avoid ...
A "what commands are useful"-question is a very opinion-based question. Some might consider command 'foo' to be very useful, but the next might consider it to be stupid.
This would quickly spark a discussion. While this discussion might be interesting, it's not a good fit for the SE format in general. I don't see why vi.SE should be an exception.
Should we encourage their use
They look cool, and definitely add value, as such. But, I also find them somewhat hard to follow, the screen jumps around a lot, and I can't manually freeze it, or go back a frame. At the same time, I have to pay attention to the keys that are being typed and what it's doing on the screen.
In other words: it's a great ...
There've been a couple of other discussions on this:
Should we have separate tags [vi] and [vim]?
Should questions and answers assume the use of Vim?
It's becoming apparent that neither vi nor vim is likely to be used at all consistently here. Meanwhile, there is considerable value in encouraging folks to use tags that reflect the platform they're using, ...
I surprised no one nominated muru yet. I think he would make for a fine moderator (I didn't want to add too many nominees last time, and expected
someone else to do it).
Muru was involved in the Area51 definition
, and has been a useful member of the site since the start of the beta, not just
Personally, I strongly dislike this guideline. I reject edits that do this on Stack Overflow and any other SE site.
When you ask a question here you're asking complete strangers on the internet to help you out. I would argue that saying "Thanks" is not just a formality, but a show of basic human decency. There is nothing wrong with being polite.
Should I post my new problems here first or if I find an answer somewhere on the interwebs should I leave my new question out of vim.SE?
Remember: A sign of any good question is that the poster has put some effort into solving it. The text for the upvote button reads:
This question shows research effort; ...
So, you should look for answers on the ...
We already have a way to share information or "tricks": asking and answering your own question. One of the first things I did when this site was launched was look in my vimrc file for these "tricks" and post them as self-answered questions. Some of them even got significantly better answers from other community members than what I wrote myself!
If I go over ...
When asking a question about a problem you will get much better answers if you
provide steps or code people can use to reproduce the problem. Those steps
Minimal – Use as little commands or code as possible that still produces the
Complete – Provide all parts needed to reproduce the problem.
Verifiable – Test the steps or code you'...
You're right, most questions are about Vim. But what if the site was just named "Vim Stack Exchange"? Then just by name it would suggest that only questions about Vim are allowed, and that all other questions would be off-topic (which they're not). Questions about original-vi or nvi are not common, but they do get asked.
Vim just so happens to be the most ...
Questions asking for tutorials do not fit anywhere on Stack Exchange. They're too broad (and hence don't fit the Q&A format), and also highly opinion-based (which makes it impossible to determine whether an answer actually answers the question).
Oh yeah, they also encourage link-only answers, which we don't want. And, they're "big list" questions ...
No, I think that such tags would be too cryptic to be useful. Why hkjl instead of hjkl? Also, case-sensitivity is a problem. Furthermore, they either presuppose that the person asking the question knows the solution, or encourage the asker to ask an excessively narrow question.
I'd much rather have cursor-movement than hkjl.