[GRLUG] Vim Group? Editors and IDEs

[Don Ellis]

I haven't pushed it very far, but a couple of other guys here (in perl
& *n*x UGs) have been pushing it nicely. I appreciate that the current
version uses common GUI commands, such as cmd-s, cmd-w, cmd-q, et al.
Wednesday night's meeting brought forward the note that the system
paste buffer is accessible from inside vim, which gives an interface
to other applications.

One extension that has been mentioned is a Firefox addon that allows
using vim commands to control Firefox, and another extension that
allows using vim to edit any (Carbon) GUI input field.

I've forwarded Bob's comment to Bil Odom, who leads most of the
vim-geeks meetings (you can see vim-geeks in Google Groups, and join
in if you want.

And, Bob, your commands summarize it pretty well. I've been using
buffers, as you say, since early on, except that now they're called
"registers" to distinguish them from another concept that is currently
being  called "buffers". As everywhere else, re-using a common term is
a popular practice in vim as well.

--Don Ellis


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

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.