I forgot o and O, which are <div>pretty handy. But again, it's</div><div>amazing how much one can</div><div>do with so few commands.</div><div><br></div><div>There must be many dozens of</div><div>editors, some optimized for editing</div>
<div>C programs, HTML, etc., but for</div><div>most the limitation will always be</div><div>how many details can you juggle</div><div>at the same time. For many, it's</div><div>perhaps more productive to get one</div>
<div>or two editors down well, and move</div><div>on.</div><div><br></div><div> -- Bob</div><div><br></div><div><br><div class="gmail_quote">On Fri, Jun 24, 2011 at 3:29 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 haven't pushed it very far, but a couple of other guys here (in perl<br>
& *n*x UGs) have been pushing it nicely. I appreciate that the current<br>
version uses common GUI commands, such as cmd-s, cmd-w, cmd-q, et al.<br>
Wednesday night's meeting brought forward the note that the system<br>
paste buffer is accessible from inside vim, which gives an interface<br>
to other applications.<br>
<br>
One extension that has been mentioned is a Firefox addon that allows<br>
using vim commands to control Firefox, and another extension that<br>
allows using vim to edit any (Carbon) GUI input field.<br>
<br>
I've forwarded Bob's comment to Bil Odom, who leads most of the<br>
vim-geeks meetings (you can see vim-geeks in Google Groups, and join<br>
in if you want.<br>
<br>
And, Bob, your commands summarize it pretty well. I've been using<br>
buffers, as you say, since early on, except that now they're called<br>
"registers" to distinguish them from another concept that is currently<br>
being called "buffers". As everywhere else, re-using a common term is<br>
a popular practice in vim as well.<br>
<font color="#888888"><br>
--Don Ellis<br>
</font><div><div></div><div class="h5"><br>
<br>
On Fri, Jun 24, 2011 at 2:00 PM, Bob Kline <<a href="mailto:bob.kline@gmail.com">bob.kline@gmail.com</a>> wrote:<br>
> vim UG?<br>
> I'm curious, how much of vim do<br>
> most people actually use?<br>
> I've been using vi for 30 years, and<br>
> I doubt I use more than two dozen<br>
> commands. I'm guessing that 99% of<br>
> the work gets done with maybe 5%<br>
> or less of the features of vi - now vim.<br>
> * Open and close a file. Maybe<br>
> close it with :q! if the file has<br>
> been mangled. Maybe write the<br>
> file out now and then with :w<br>
> * yy or Nyy to yank a line or lines.<br>
> * p to put some lines in place.<br>
> * a, i, A, and I to add some stuff.<br>
> * ^ and $ to position at the beginning<br>
> or end fo a line.<br>
> * cw or Ncw to change a word or words.<br>
> * dd, dw, D, x, X, to remove some stuff.<br>
> * :r file to, well, read in a file at a specific<br>
> place.<br>
> * :1,$s/string1/string2/g to replace something<br>
> everywhere in a file.<br>
> * / and ? to find something, and n to find<br>
> another occurrence.<br>
> Even that much seems to get one a long<br>
> way. On rare occasions I've used buffers,<br>
> edited multiple files, etc.<br>
> What other things do people find handy?<br>
> -- Bob<br>
><br>
> On Fri, Jun 24, 2011 at 2:42 PM, Don Ellis <<a href="mailto:don.ellis@gmail.com">don.ellis@gmail.com</a>> wrote:<br>
>><br>
>> 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>
>><br>
>> --Don Ellis<br>
>> St Louis (MO)<br>
>><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<br>
>> >> 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<br>
>> >> 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.