vim UG? <div><br></div><div>I'm curious, how much of vim do</div><div>most people actually use?</div><div><br></div><div>I've been using vi for 30 years, and</div><div>I doubt I use more than two dozen</div><div>commands. I'm guessing that 99% of</div>
<div>the work gets done with maybe 5%</div><div>or less of the features of vi - now vim.</div><div><br></div><div>* Open and close a file. Maybe </div><div> close it with :q! if the file has</div><div> been mangled. Maybe write the</div>
<div> file out now and then with :w</div><div><br></div><div>* yy or Nyy to yank a line or lines.</div><div><br></div><div>* p to put some lines in place.</div><div><br></div><div>* a, i, A, and I to add some stuff. </div>
<div><br></div><div>* ^ and $ to position at the beginning</div><div> or end fo a line.</div><div><br></div><div>* cw or Ncw to change a word or words.</div><div><br></div><div>* dd, dw, D, x, X, to remove some stuff.</div>
<div><br></div><div>* :r file to, well, read in a file at a specific</div><div> place.</div><div><br></div><div>* :1,$s/string1/string2/g to replace something</div><div> everywhere in a file.</div><div><br></div><div>* / and ? to find something, and n to find</div>
<div> another occurrence.</div><div><br></div><div>Even that much seems to get one a long</div><div>way. On rare occasions I've used buffers,</div><div>edited multiple files, etc.</div><div><br></div><div>What other things do people find handy?</div>
<div><br></div><div> -- Bob</div><div><br></div><div><br><div class="gmail_quote">On Fri, Jun 24, 2011 at 2:42 PM, Don Ellis <span dir="ltr"><<a href="mailto:don.ellis@gmail.com">don.ellis@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">I had been using BBEdit quite a lot, until the local (St Louis MO) Vim<br>
UG got started. Fairly active, and we've had presentations at LUG and<br>
Unix UG meetings, besides the vim-geeks meetings. Now, I'm mostly<br>
using MacVim for casual (or formal) editing. At the vim-geeks meetings<br>
and presentations by the leader, I've been learning lots of new<br>
commands and tools beyond basic vi.<br>
<br>
One big reason was I started using vi back in mid to early '80s, and I<br>
keep trying to use vi commands in GUI editors. Cmd-Z is my friend. ;-)<br>
<font color="#888888"><br>
--Don Ellis<br>
St Louis (MO)<br>
</font><div><div></div><div class="h5"><br>
<br>
On Fri, Jun 24, 2011 at 10:49 AM, Ben Rousch <<a href="mailto:brousch@gmail.com">brousch@gmail.com</a>> wrote:<br>
> On Fri, Jun 24, 2011 at 11:45 AM, Topher <<a href="mailto:topher@codeventure.net">topher@codeventure.net</a>> wrote:<br>
>><br>
>> I tweeted about this, but didn't post to the list, so I will now. This<br>
>> article was amazingly enlightening to me:<br>
>> <a href="http://stevelosh.com/blog/2010/09/coming-home-to-vim/" target="_blank">http://stevelosh.com/blog/2010/09/coming-home-to-vim/</a><br>
>><br>
>> I just found it the other day, and he talks about doing things with vim I'd<br>
>> never heard of, which is impressive for a 15 year user.<br>
>><br>
>> It's ostensibly about why he switched from textmate to vim, but his reasons<br>
>> are each great tutorials in themselves.<br>
>><br>
>> It's really about why vim is a really great editor.<br>
><br>
> That article is why some of you saw me trying out Vim (again) at<br>
> Wednesday's social meeting. Thanks Topher.<br>
><br>
> --<br>
> Ben Rousch<br>
> <a href="mailto:brousch@gmail.com">brousch@gmail.com</a><br>
> <a href="http://clusterbleep.net/" target="_blank">http://clusterbleep.net/</a><br>
<br>
--<br>
This message has been scanned for viruses and<br>
dangerous content by MailScanner, and is<br>
believed to be clean.<br>
<br>
_______________________________________________<br>
grlug mailing list<br>
<a href="mailto:grlug@grlug.org">grlug@grlug.org</a><br>
<a href="http://shinobu.grlug.org/cgi-bin/mailman/listinfo/grlug" target="_blank">http://shinobu.grlug.org/cgi-bin/mailman/listinfo/grlug</a><br>
</div></div></blockquote></div><br></div>
<br />--
<br />This message has been scanned for viruses and
<br />dangerous content by
<a href="http://www.mailscanner.info/"><b>MailScanner</b></a>, and is
<br />believed to be clean.