I run vim with "--noplugin -u NONE -N" which, if I remember correctly, should put it in nocompatible mode. I don't know if it makes any difference. Anyway I'll check the patch, but unfortunately I won't be able to do that before Monday.
Thanks for the help! Il giorno ven 28 nov 2014 alle 19:32 Marcin Szamotulski <[email protected]> ha scritto: > On 05:00 Fri 28 Nov , Matteo Cavalleri wrote: > > > This patch made a big change in how ranges are handled, thus it's > > > possible that it introduced a bug. > > > > > > Can you reproduce it without any plugins? > > > With a simple user command perhaps? > > > > create and source this file > > > > ------------------------ > > function! Test(f,l) > > echom a:f." - ".a:l > > endfunction > > command! -range=% RangeTest call Test(<line1>, <line2>) > > ------------------------ > > > > then select a couple of lines and do: > > > > :'<,'>RangeTest > > > > and you can see the error I reported, plus the result is always "1 - 5" > > I cannot reproduce it with `vim -u NONE`. If I select a few lines and > yank them then > :'<,'>RangeTest > always shows the correct range. I also tested that the :'[,']RangeTest > works fine. > > But I think we should apply the attached patch. Matteo can you please > check if this solves the issue for you. > > Best regards, > Marcin > -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
