On May 26, 2012, at 8:44 PM, Eric Weir wrote:
> 
>> On May 26, 2012, at 11:44 AM, sc wrote:
>> 
>> the bad news is you've just implied you don't know how to use vim's
>> extensive help system (or maybe you're intimidated by it?)
>> 
>>   :h :e
>> 
>> would have answered that for you -- i recommend spending some time
>> familiarizing yourself with the help system -- learn about helpgrep,
>> and try it out with
>> 
>>   :helpgrep filetype detection
>> 
>> there are about 24 hits on that specific string, and will take you to
>> many interesting places in Help as you :cn your way through them
> 
> Thanks, sc. I do know how to use it---sorta. I know how to call up the files 
> and navigate around in them. The problem is that I don't understand most of 
> what's explained when I seek help from it. I don't avoid it. I often do check 
> before asking for help. [Don't think I did so this time.] But usually end up 
> having to ask for help anywat. On the other hand, I find the FAQs very 
> helpful.
> 
> That said, I will do as you suggest---after check the help on "help" versus 
> "helpgrep."

Ok, I think I know the difference between help and helpgrep. Help takes you to 
[the first?] item tagged with the string entered with the command. Helpgrep 
makes a list of all instances in which the string occurs. [Suspect that's not 
quite right, but it's what I've taken from what I read.] 

The problem for me with the latter is that the instances seem to go on 
interminably, with no clear demarcation---at least that's evident to 
me---between the list of instances of the string and other help topics. But the 
initial instances are clear and I will study them.

------------------------------------------------------------------------------------------
Eric Weir
1111 Clairemont Avenue J3 ~ Decatur, GA 30030
404-636-6142 ~ eew...@bellsouth.net

-- 
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

Reply via email to