Greetings!
I have a minor issue with Ruby syntax highlighting in vim, and was
wondering whether others have similar problems. Let's take the
following code:
until true
3.time do |f|
p f
end
end
The last ``end'' is not highlighted. I assume that it is an issue
with the stack counting the highlights (possibly something along the
lines of ``stack = 1'' instead of ``stack += 1'', as
until true
3.time do |f|
[ "a", "b", "c" ].each do |g|
p [ f, g ]
end
end
end
has the last two ``end''s without highlighting. Lastly, I checked if
highlighting works properly outside of the until ... end block, so I
tested
def foo
until true
3.time do |f|
p f
end
end
end
The highlighting is off by 1 (the 2nd ``end'' is highlighted as
matching the method definition).
My vim version is 6.3.78, from the Debian unstable apt repository.
Would anyone else be so kind as to attempt to reproduce this and
confirm that it is not just an issue with my machine?
Many regards....
-CWS
Not so exactly, but I've had similar problem with 'end'.
In cases you suggested, I couldn't reproduce those with version
6.3.84(Gentoo), 6.3.46(Ubuntu Hoary).
As for me, I'd be bothered when removing lines in the middle of
modules or classes.
···
On 8/9/05, Claus Spitzer <docboobenstein@gmail.com> wrote:
Greetings!
I have a minor issue with Ruby syntax highlighting in vim, and was
wondering whether others have similar problems. Let's take the
following code:
until true
3.time do |f|
p f
end
end
The last ``end'' is not highlighted. I assume that it is an issue
with the stack counting the highlights (possibly something along the
lines of ``stack = 1'' instead of ``stack += 1'', as
until true
3.time do |f|
[ "a", "b", "c" ].each do |g|
p [ f, g ]
end
end
end
has the last two ``end''s without highlighting. Lastly, I checked if
highlighting works properly outside of the until ... end block, so I
tested
def foo
until true
3.time do |f|
p f
end
end
end
The highlighting is off by 1 (the 2nd ``end'' is highlighted as
matching the method definition).
My vim version is 6.3.78, from the Debian unstable apt repository.
Would anyone else be so kind as to attempt to reproduce this and
confirm that it is not just an issue with my machine?
Many regards....
-CWS
--
http://nohmad.sub-port.net
This was fixed a long time ago but unfortunately didn't make it upstream
for the vim6 release. I'd suggest updating to the latest release of
vim-ruby which you can find at http://vim-ruby.rubyforge.org/
There should hopefully be a new release of this in the next week or
so...
<snip>
Regards,
Doug
···
On Tue, Aug 09, 2005 at 11:01:40PM +0900, Claus Spitzer wrote:
Greetings!
I have a minor issue with Ruby syntax highlighting in vim, and was
wondering whether others have similar problems. Let's take the
following code:
until true
3.time do |f|
p f
end
end
The last ``end'' is not highlighted.
it does this with 6.3.86 (compiled with vc++6.0 on winxp) also.
i got tired of that. it's why i use arachno-ruby now...
···
Claus Spitzer wrote on 8/9/2005 10:01 AM:
I have a minor issue with Ruby syntax highlighting in vim,
My vim version is 6.3.78, from the Debian unstable apt repository.
Would anyone else be so kind as to attempt to reproduce this and
confirm that it is not just an issue with my machine?
--
http://home.cogeco.ca/~tsummerfelt1
telnet://ventedspleen.dyndns.org
it's not working for 6.3.86, compiled from source and all current
patches applies (on windows as i mentioned in a prev. msg)
···
Doug Kearns wrote on 8/9/2005 11:48 AM:
The last ``end'' is not highlighted.
This was fixed a long time ago but unfortunately didn't make it upstream
for the vim6 release.
--
http://home.cogeco.ca/~tsummerfelt1
telnet://ventedspleen.dyndns.org
Sorry for the late reply.
>>The last ``end'' is not highlighted.
> This was fixed a long time ago but unfortunately didn't make it upstream
> for the vim6 release.
it's not working for 6.3.86, compiled from source and all current
patches applies (on windows as i mentioned in a prev. msg)
This is not really how the vim development model works. Having the
latest version of Vim itself is certainly no guarantee that you have the
latest runtime files. Obviously any major, or point, release of Vim
_should_ be an exception. 
If you're having problems with any runtime file your first point of call
should always be the individual maintainer to make sure you are using
the latest version. The easiest way to do so is to check the URL header
which should point to the latest version or, if that is missing, send
the maintainer an email.
There's currently far too much manual updating of these files to ever
assume they're all in sync at a given point in time.
Regards,
Doug
···
On Wed, Aug 10, 2005 at 10:32:15PM +0900, tony summerfelt wrote:
Doug Kearns wrote on 8/9/2005 11:48 AM: