From: Jim Freeze <jim@...>
Date: 2002-08-01T01:07:32+09:00
Subject: Re: Style question

On Thu, Aug 01, 2002 at 12:59:01AM +0900, Gavin Sinclair wrote:
> What's really unfortunate, though, is that Vim has some killer features
> dealing with {...} blocks (on account of its C heritage and the plain
> ubiqity of such blocks.
> 
> For example, you can delete, change, indent, or do whatever you like to the
> contents of {...} (or (...), [...], etc.) in an instant, no matter where the
> cursor is in the block.
> 
> Obviously, this functionality does not apply to do...end blocks.  Despite
> this loss, I still use do...end because it seems more fitting for Ruby.
> 

I decided some time ago not to be a slave to the language, but
to be a slave to my editor. :)

I have chosen the lowest common demoninator, ie, I use spaces
instead of tabs and I use {} instead of do end. This lets
me edit easily whether I use vi, vim, gvim, emacs, 
emacs+ruby extensions, etc, and have my code still look uniform
in any editor,


Jim

> 
> 
> > On Tuesday 30 July 2002 09:53 pm, Jim Freeze wrote:
> > > On Tue, Jul 30, 2002 at 11:19:52PM +0900, Michael Campbell wrote:
> > > > Is there an accepted standard as to when to use {} vs do/end?
> > >
> > > I personally like the {} for the simple reason that it is easy
> > > to test for matching pairs in vi.
> >
> > Note that matchit will also let you bounce between e.g. do/end pairs
> > in Vim.
> >
> > --
> > Ned Konz
> > http://bike-nomad.com
> > GPG key ID: BEEA7EFE
> 

-- 
Jim Freeze
If only I had something clever to say for my comment...
~