I know: you want to be a good #vim citizen; you want to be a
good vimmer; you want to learn and grow and solve your
problems in a timely manner and do so in a safe and
supportive environment filled with smart, caring and funny
peers.
I know; we all do. And we all can. Here’s how:
Both for reasons of courtesy to others and self-edification, it’s important to try to find the answers to your own questions yourself before asking others on #vim. But just as important is how you ask:
For simple, easy and short examples, asking inline is acceptable and preferred, but if your problem is dense or requires more than a couple lines of data, using a pastebin service is preferred. Github’s gist is popular, but any decent ad-free pastebin will be happily tolerated. The format of your pastebin is also important. Here is an excellent example: https://gist.github.com/2759774
In fairness, I have rarely seen such bad behaviour on #vim; it’s generally one of the most polite chat rooms I’ve ever seen. Let’s keep it that way! :-)
I know; we all do. And we all can. Here’s how:
Help Yourself
Vim has an awesome built-in manual filled with more answers than you have questions. Almost every problem you have is addressed somewhere within its many chapters. Unfortunately, newcomers often can’t find what they’re looking for in the manual, or don’t understand the answer because of a lack of jargon or fundamental Vim-specific knowledge. This feeling of inaccessibility passes over time as you level up in Vim, but can be debilitating to the beginner. But despair not! When you don’t understand something in the manual, then that is the time for asking on #vim, but more on that later. First, here are some tips for helping yourself to some Vim love:I use the loose term manual here to treat the reference-manual and user-guide as a whole, just as the built in tools for navigating them do. |
-
:help topic will jump to topic within the
manual.
-
:helpgrep pattern will search for all occurrences
of pattern throughout the manual. Use :cope to
open the quickfix window of search results.
-
There is a decent FAQ: http://vimhelp.appspot.com/vim_faq.txt.html
-
The #vim channel has a fact bot called vimgor filled with
answers to common problems. These facts are often keyed on
weird terms that must be supplied to vimgor precisely to
elicit their associated gems of wisdom, which is
practically useless to the uninitiated. Thankfully, vimgor
supports a listfacts interface that will return all
known facts containing the given term, e.g:
/msg vimgor listfacts file
will list all known keys containing file.
You should explore vimgor using either /msg or /query
to limit interference on the #vim channel. Feel free to call upon vimgor directly from within #vim if you are using it to answer someone else’s question. Here are some additional tools in that vein:
|
Ask For Help
So you’ve looked in the manual and can’t find an answer, or don’t understand the answer; you’ve looked at the FAQs and checked in with vimgor to no avail. Now is the time to ask for help on #vim. Alternatively, ask reddit's vim channel. The guidelines for asking on #vim apply equally well for reddit's forum, of course.Both for reasons of courtesy to others and self-edification, it’s important to try to find the answers to your own questions yourself before asking others on #vim. But just as important is how you ask:
For simple, easy and short examples, asking inline is acceptable and preferred, but if your problem is dense or requires more than a couple lines of data, using a pastebin service is preferred. Github’s gist is popular, but any decent ad-free pastebin will be happily tolerated. The format of your pastebin is also important. Here is an excellent example: https://gist.github.com/2759774
Etiquette
It’s obvious to most people that asking politely will yield better responses; some people need to be told explicitly. The good folk of #vim freely donate their time and energy to helping others discover the joy of being a vimmer. They delight in sharing their arcane knowledge with interested learners and inquisitive minds. In case you’re having trouble reading between the lines here, don’t approach #vim with these attitudes:-
impatience or unwillingness to learn: You don’t care to
read the :help topic provided, you just want the solution
to your exact problem RIGHT NOW. Nothing upsets a vimmer
more. The :help is extremely well written if not a bit
obtuse for newcomers, but we’ll help you understand those
intricacies — very rarely is someone told to rtfm and then
left to drown in their own incomprehension.
-
rudeness or ungratefulness: diagnosing your problem might
take some time and several steps requiring your
participation. If you get frustrated at this or interact
poorly then your chances of continued support diminish
quickly. Be nice, get nice; say please and thank you.
Teach as if your mentor is watching from the corner.The analogy here is: ask as if you weren’t sitting behind a terminal; ask as if your mum or boss or teacher or doctor or someone you respect were listening.
In fairness, I have rarely seen such bad behaviour on #vim; it’s generally one of the most polite chat rooms I’ve ever seen. Let’s keep it that way! :-)
No comments:
Post a Comment