From gsinclair at gmail.com  Sat Jul 21 21:50:12 2007
From: gsinclair at gmail.com (Gavin Sinclair)
Date: Sun, 22 Jul 2007 11:50:12 +1000
Subject: Indent bug and probable solution reported
Message-ID: <a76b05c10707211850s1f13e4c2obec590d4cea30f4a@mail.gmail.com>

Hi guys,

I was notified of this via email: a new indent bug on the tracker.

Can someone please take a look at it?  There's a fix ready to go that
hopefully works.

   http://rubyforge.org/tracker/?func=detail&atid=145&aid=12421&group_id=16

Cheers,
Gavin

From vim-ruby-devel at tpope.info  Sat Jul 21 23:19:17 2007
From: vim-ruby-devel at tpope.info (Tim Pope)
Date: Sat, 21 Jul 2007 22:19:17 -0500
Subject: Indent bug and probable solution reported
In-Reply-To: <a76b05c10707211850s1f13e4c2obec590d4cea30f4a@mail.gmail.com>
References: <a76b05c10707211850s1f13e4c2obec590d4cea30f4a@mail.gmail.com>
Message-ID: <20070722031917.GZ4147@michael.tpope.us>

On Sun, Jul 22, 2007 at 11:50:12AM +1000, Gavin Sinclair wrote:
> Hi guys,
> 
> I was notified of this via email: a new indent bug on the tracker.
> 
> Can someone please take a look at it?  There's a fix ready to go that
> hopefully works.
> 
>    http://rubyforge.org/tracker/?func=detail&atid=145&aid=12421&group_id=16

I addressed this just a few days earlier.  I closed the report with a
comment stating a such.

Cheers,
Tim

From gsinclair at gmail.com  Fri Jul 27 10:06:24 2007
From: gsinclair at gmail.com (Gavin Sinclair)
Date: Sat, 28 Jul 2007 00:06:24 +1000
Subject: Indent bug and probable solution reported
In-Reply-To: <20070722031917.GZ4147@michael.tpope.us>
References: <a76b05c10707211850s1f13e4c2obec590d4cea30f4a@mail.gmail.com>
	<20070722031917.GZ4147@michael.tpope.us>
Message-ID: <a76b05c10707270706s4a78b8ccu4eea8acef53ac5e5@mail.gmail.com>

Excellent.  Thanks!

On 7/22/07, Tim Pope <vim-ruby-devel at tpope.info> wrote:
> On Sun, Jul 22, 2007 at 11:50:12AM +1000, Gavin Sinclair wrote:
> > Hi guys,
> >
> > I was notified of this via email: a new indent bug on the tracker.
> >
> > Can someone please take a look at it?  There's a fix ready to go that
> > hopefully works.
> >
> >    http://rubyforge.org/tracker/?func=detail&atid=145&aid=12421&group_id=16
>
> I addressed this just a few days earlier.  I closed the report with a
> comment stating a such.
>
> Cheers,
> Tim
> _______________________________________________
> vim-ruby-devel mailing list
> vim-ruby-devel at rubyforge.org
> http://rubyforge.org/mailman/listinfo/vim-ruby-devel
>

From gsinclair at gmail.com  Thu Aug 30 00:29:01 2007
From: gsinclair at gmail.com (Gavin Sinclair)
Date: Thu, 30 Aug 2007 14:29:01 +1000
Subject: Comments and indenting
Message-ID: <a76b05c10708292129q6ce17d1fo865150f946246e18@mail.gmail.com>

[Forwarded message from Brian Doyle.  Just wondering if anyone has a solution.]

I'm new to vim and ruby so I'm not actually sure where the problem.
First off thanks for writing the ruby.vim code!  I've been using it
quite a bit and it's been great.  I do have one issue that doesn't
seem to be quite right.  When I start a comment above a method the #
always moves over all the way to the right.

class Blah

   # <start comments>
   def do_something

   end
end

Immediately after entering the # it moves to:

class Blah

#
   def do_something

   end
end

Not sure if this is a problem with ruby.vim or what exactly.  i
noticed that this only happens after doing a C-O or C-o and then type
the #.   Thanks for your help.

From now at bitwi.se  Thu Aug 30 02:55:44 2007
From: now at bitwi.se (Nikolai Weibull)
Date: Thu, 30 Aug 2007 08:55:44 +0200
Subject: Comments and indenting
In-Reply-To: <a76b05c10708292129q6ce17d1fo865150f946246e18@mail.gmail.com>
References: <a76b05c10708292129q6ce17d1fo865150f946246e18@mail.gmail.com>
Message-ID: <dbfc82860708292355h666d058an516a97a2cc08f22d@mail.gmail.com>

On 8/30/07, Gavin Sinclair <gsinclair at gmail.com> wrote:
> [Forwarded message from Brian Doyle.  Just wondering if anyone has a solution.]
>
> I'm new to vim and ruby so I'm not actually sure where the problem.
> First off thanks for writing the ruby.vim code!  I've been using it
> quite a bit and it's been great.  I do have one issue that doesn't
> seem to be quite right.  When I start a comment above a method the #
> always moves over all the way to the right.
>
> class Blah
>
>    # <start comments>
>    def do_something
>
>    end
> end
>
> Immediately after entering the # it moves to:

[the beginning of the line]

:h 'indentkeys'

You seem to have messed up your setup.  Make sure your 'indentkeys'
setting is set to

  0{,0},0),0],!^F,o,O,e

> Not sure if this is a problem with ruby.vim or what exactly.  i
> noticed that this only happens after doing a C-O or C-o and then type
> the #.   Thanks for your help.

C-O/C-o?

  nikolai

From vim-ruby-devel at tpope.info  Thu Aug 30 09:49:56 2007
From: vim-ruby-devel at tpope.info (Tim Pope)
Date: Thu, 30 Aug 2007 08:49:56 -0500
Subject: Comments and indenting
In-Reply-To: <a76b05c10708292129q6ce17d1fo865150f946246e18@mail.gmail.com>
References: <a76b05c10708292129q6ce17d1fo865150f946246e18@mail.gmail.com>
Message-ID: <20070830134956.GA4524@michael.tpope.us>

> Immediately after entering the # it moves to:
> 
> class Blah
> 
> #
>    def do_something
> 
>    end
> end

Sounds like 'smartindent' to me.  The ruby ftplugin doesn't set it;
the user vimrc is the most likely culprit.

Cheers,
Tim

From now at bitwi.se  Thu Aug 30 10:51:29 2007
From: now at bitwi.se (Nikolai Weibull)
Date: Thu, 30 Aug 2007 16:51:29 +0200
Subject: Comments and indenting
In-Reply-To: <20070830134956.GA4524@michael.tpope.us>
References: <a76b05c10708292129q6ce17d1fo865150f946246e18@mail.gmail.com>
	<20070830134956.GA4524@michael.tpope.us>
Message-ID: <dbfc82860708300751n2f3798edp7a433cf2a1295cc7@mail.gmail.com>

On 8/30/07, Tim Pope <vim-ruby-devel at tpope.info> wrote:
> > Immediately after entering the # it moves to:
> >
> > class Blah
> >
> > #
> >    def do_something
> >
> >    end
> > end
>
> Sounds like 'smartindent' to me.  The ruby ftplugin doesn't set it;
> the user vimrc is the most likely culprit.

Actually, the latest version should be unsetting 'smartindent' (which
should be done by the filetype-handling code in my opinion, but Bram
didn't agree with me).  Strange.  Perhaps he's using an old version.
Bug reports against old versions are always grade A.

  nikolai