On Oct 21, 2006, at 11:46 AM, Java Bob wrote:
Gary Johnson wrote:
I don't think that's true. Vim :help comprises two manuals:
Vim User Manual - :help user-manual
Vim Reference Manual - :help reference
This is even discussed in ":help 01.1". The User Manual is written
in a different style th
Gary Johnson wrote:
> I don't think that's true. Vim :help comprises two manuals:
>
> Vim User Manual - :help user-manual
> Vim Reference Manual - :help reference
>
> This is even discussed in ":help 01.1". The User Manual is written
> in a different style than the Reference Manual and is more re
Gary Johnson wrote:
I don't think that's true. Vim :help comprises two manuals:
Vim User Manual - :help user-manual
Vim Reference Manual - :help reference
This is even discussed in ":help 01.1". The User Manual is written
in a different style than the Reference Manual and is more readable.
I be
Meghdad Azriel wrote:
[...]
I wanna be a guru in a blink of eyes :P
[...]
You can't: TANSTAAFL. (And if you haven't read R. A. Heinlein's /The Moon is a
Harsh Mistress/, TANSTAAFL is an acronym for: 'T ain't no such thing as a free
lunch.)
The only way to become a guru is by hard labour: at
that between the tutor and help, tere are also the vimFAQ
>> and vimtips (both at vim-online).
>>
>> You seem to have interesting ideas. Maybe you should discuss them
>> with the FAQ maintainer.
>>
>>
>> Best regards,
>> Tony.
> Hi,
>
> As one of the potential beneficiaries of the proposed document, I'd
> like to add that what I have a hard time finding are the 'philosophy'
> items mentioned in the proposal. I'd like to get a better
> understanding of the way Vim views text, what the modes are for,
> etc. i.e. the bigger picture.
>
> I find :help to be excellent when I know what question to ask, but
> often lack the context to know where best to look. Reading this list
> helps fill in the concepts in an ad hoc sort of way, but a more
> systematic exposition would be nice.
>
> HTH, Hal
>
>
>
>
--
View this message in context:
http://www.nabble.com/Fighting-with-comments-tf2467964.html#a6924420
Sent from the Vim - General mailing list archive at Nabble.com.
On Oct 20, 2006, at 1:39 AM, A.J.Mechelynck wrote:
vim wrote:
Hi everobody,
I recently had a very similar conversation with three guys on #vim
(irc.freenode.net).
Basicaly, there is two official help for Vim:
- the vimtutor
- :help
And that's basically it.
:help being your Vim dictionn
On 2006-10-20, vim <[EMAIL PROTECTED]> wrote:
> Hi everobody,
>
> I recently had a very similar conversation with three guys on #vim
> (irc.freenode.net).
>
> Basicaly, there is two official help for Vim:
>- the vimtutor
>- :help
>
> And that's basically it.
I don't think that's true.
On 10/18/06, Gary Johnson <[EMAIL PROTECTED]> wrote:
The way to fix this problem is to create two new directories:
$VIM\vimfiles\after
$VIM\vimfiles\after\ftplugin
on Windows or
~/.vim/after
~/.vim/after/ftplugin
on Unix. Then create a new file in the after/ftplugin directory
see ":help quickfix.txt"). Then the
>>> following commands may come useful:
>>>
>>> :cn[ext]
>>> :cp[revious] or :cN[ext]
>>> :cnf[ile]
>>> :cpf[ile] or :cNf[ile]
>>> :cfir[st] or :cr[ewind]
>>> :cla[st]
>>>
>>> to navigate the list, displaying the helpfiles with the cursor on a
>>> match;
>>>
>>> :cope[n]
>>>
>>> to open the list of matching lines in its own split-window, where you
>>> can position the cursor on any of those lines then hit to see
>>> the same line in context in its helpfile;
>>>
>>> :ccl[ose]
>>>
>>> to close the quickfix window, even if it is not the current window.
>>> (Brackets represent the optional part of the command names: e.g.
>>> ":cp[revious]" means that the ":cprevious" command can be abbreviated
>>> to any of :cp :cpr :cpre :cprev etc.)
>>>
>>> If you often use the ":helpgrep" command and/or other quickfix
>>> commands such as ":make" ":vimgrep" etc., you may find the following
>>> mappings handy (replace the left-hand side by whatever suits you):
>>>
>>> :map :cnext
>>> :map:cprev
>>>
>>>
>>> Best regards,
>>> Tony.
>>>
>>
>>
>>
>
>
--
View this message in context:
http://www.nabble.com/Fighting-with-comments-tf2467964.html#a6916228
Sent from the Vim - General mailing list archive at Nabble.com.
st, displaying the helpfiles with the cursor on a
>> match;
>>
>> :cope[n]
>>
>> to open the list of matching lines in its own split-window, where you
>> can position the cursor on any of those lines then hit to see
>> the same line in context in its
vim <[EMAIL PROTECTED]> 写于 2006-10-20 15:50:36:
> Hi everobody,
>
> I believe that there is room between vimtutor and :help to have some
> beginner to intermediate tutorial that will take you by the hand and
> bring you through the Vim universe in a nice and easy way.
There already is one close t
vim wrote:
Hi everobody,
I recently had a very similar conversation with three guys on #vim
(irc.freenode.net).
Basicaly, there is two official help for Vim:
- the vimtutor
- :help
And that's basically it.
:help being your Vim dictionnary/encyclopedia/bible, it's very complete
and ha
Hi everobody,
I recently had a very similar conversation with three guys on #vim
(irc.freenode.net).
Basicaly, there is two official help for Vim:
- the vimtutor
- :help
And that's basically it.
:help being your Vim dictionnary/encyclopedia/bible, it's very complete
and has everything
Meghdad Azriel wrote:
I was just kidding ;)
I know that they are not secret but, they´re not that intuitive... and i´m
still learning how to use that help effectivelly...
maybe I neet to read those basic files with care...
[...]
To use the help effectively, one should learn to use the tools
ivision
> | Spokane, Washington, USA
>
>
--
View this message in context:
http://www.nabble.com/Fighting-with-comments-tf2467964.html#a6905899
Sent from the Vim - General mailing list archive at Nabble.com.
On 2006-10-19, eric1235711 <[EMAIL PROTECTED]> wrote:
> this worked too
>
> I think this is better, help tells that this formatoptions is specific to
> coments and things...
>
> But I´m getting disgusted of these "secret and magic commands"...
Secret? You might find it helpful to look at
:
On 2006-10-19, eric1235711 <[EMAIL PROTECTED]> wrote:
> here it's in this way:
> C:/Program Files/Vim
> and it contains vim70/ and vimfiles/
>
> Oh, thanks, Gary! it worked!!!
>
> But I didn´t like it!!!
>
> when I changed C:/Program Files/Vim/vimfiles/ftplugin/php.vim it stoped
> 'autowriting'
after\ftplugin
>>
>> on Windows or
>>
>> ~/.vim/after
>> ~/.vim/after/ftplugin
>>
>> on Unix. Then create a new file in the after/ftplugin directory
>> named php.vim and put in it those commands that fix the problem,
>> e.g.,
>>
>>
See:
>
> :help ftplugin-overrule
> :help ftplugin
>
> HTH,
> Gary
>
> --
> Gary Johnson | Agilent Technologies
> [EMAIL PROTECTED] | Wireless Division
> | Spokane, Washington, USA
>
>
--
View this message in context:
http://www.nabble.com/Fighting-with-comments-tf2467964.html#a6896080
Sent from the Vim - General mailing list archive at Nabble.com.
x/php.vim but I just don´t know where correct it...
>
> Do you have any idea of how I fix it?
>
--
View this message in context:
http://www.nabble.com/Fighting-with-comments-tf2467964.html#a6895768
Sent from the Vim - General mailing list archive at Nabble.com.
--- Gary Johnson <[EMAIL PROTECTED]> wrote:
> On 2006-10-18, eric1235711 <[EMAIL PROTECTED]> wrote:
>
> > Yakov Lerner-3 wrote:
> > >
> > > On 10/18/06, eric1235711 <[EMAIL PROTECTED]> wrote:
> > >>
> > >> Hello
> > >>
> > >> I´m PHP programmer and I started programming in gVim last weak, and I
On 2006-10-18, eric1235711 <[EMAIL PROTECTED]> wrote:
> Yakov Lerner-3 wrote:
> >
> > On 10/18/06, eric1235711 <[EMAIL PROTECTED]> wrote:
> >>
> >> Hello
> >>
> >> I´m PHP programmer and I started programming in gVim last weak, and I´m
> >> liking it very much
> >>
> >> But I got a trouble...
> >
/php.vim but I just don´t know where correct it...
>>
>> Do you have any idea of how I fix it?
>
> Does this help:
>:set tw=0
> ?
>
> Yakov
>
>
--
View this message in context:
http://www.nabble.com/Fighting-with-comments-tf2467964.html#a6884075
Sent from the Vim - General mailing list archive at Nabble.com.
On 10/18/06, eric1235711 <[EMAIL PROTECTED]> wrote:
Hello
I´m PHP programmer and I started programming in gVim last weak, and I´m
liking it very much
But I got a trouble...
When I´m commenting (// or /* or #) and I type it breaks the line
automatically. Always I start a comment, i have to go
:
http://www.nabble.com/Fighting-with-comments-tf2467964.html#a6880708
Sent from the Vim - General mailing list archive at Nabble.com.
25 matches
Mail list logo
