$curbuf.number is sometimes become zero

Question

$curbuf.number is sometimes become zero

Closed this issue 7 years ago · 3 comments

hron84 commented 13 years ago

Hi!

I ran into this issue: https://wincent.com/issues/1617

Could you do some workaround for this?

It currently breaks this plugin to work on my 32bit system.

Answer 1 · 2012-04-07T20:20:10.000Z

Yeah, that's frustrating. It's difficult for me to include a workaround in the lusty plugins - I don't have a 32-bit system on which to test. (Happy to accept a patch, though.) The solution suggested in that bug is to rebuild Vim with --disable-largefile, or to use a more recent version of Vim that doesn't have this bug. For now that's probably what I'd advocate as well.

Answer 2 · 2012-04-08T14:37:19.000Z

@sjbach i currently using more recent version of vim, so it is solved for me. However, in that issue you can see a recommendation about $curbuf.name to work around this issue. Since $curbuf.number never can be zero, you can implement this way as a fallback mechanism.

Answer 3 · 2018-02-13T18:43:01.000Z

This is a legitimate issue, but in 2018 the population of Vim users on 32-bit platforms has gotta be tiny. Closing for convenience.