On Sep 24, 6:03 pm, Wincent Colaiuta <
w...@wincent.com> wrote:
> Hi,
>
> Originally posted to vim_use some time ago:
>
>
> Posting again here as it seems a more appropriate forum for bug
> reports.
>
> I'm the author of the Command-T plug-in, which is a Vim plugin partly
> written in Ruby:
>
>
https://wincent.com/products/command-t
>
> I've received multiple reports from people on different platforms that
> there is breakage running under 7.3 on their platform (I'm afraid I
> can't reproduce on Mac OS X though):
>
>
https://wincent.com/issues/1617
>
> The apparent cause is that, for them, evaluating "$curbuf.number"
> under Ruby _always_ returns 0, when it is supposed to return a
> positive integer buffer number. To test, just do this:
>
> :ruby puts $curbuf.number
>
> If you're on an affected platform/Vim, you'll always see 0 regardless
> of which buffer is current. Otherwise you'll see some positive
> integer.
>
> So two questions:
>
> - Is this a known bug in 7.3?
>
> - And if it's not a known issue, what information can I gather from
> these users to help troubleshoot this?
>
> Cheers,
> Wincent
problem. It adds support for the --enable-largefile and --disable-
largefile configure flags. Compiling the latest version of Vim using --