Hi Bram!
On Mo, 09 Nov 2009, Bram Moolenaar wrote:
> Christian Brabandt wrote:
> > Open Vim with any file:
> > ~$ vim -u NONE -U NONE -N foobar
> > :exe "normal V\<ESC>"
> > :echo getpos("'>")
> > [0, 1, 2147483647, 0]
> >
> > This does look like an integer overflow. Is this a bug or feature? I
> > would consider that a bug, because the column is too large (or even
> > negative) but before reporting it at vim_dev wanted to ask here.
> >
> > Interestingly col("'>") does not suffer from this overflow and reports
> > the correct column.
> >
> > Oh, version: 7.2.284 and I get the same error with a 7.1 build.
> > Operating system is Windows in both cases. Haven't tested on linux yet.
>
> This is not an error, it's the normal value for the maximum column. It
> means the position is at the end of the line. The difference with the
> real column number is that it works like the "$" command.
And this value can be negative?
Should that be added to the documentation?
regards,
Christian
--
• I'm always right. This time I'm just even more right than usual.
Torvalds, Linus (2005-07-14).
--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---
