On Thu, Aug 08, 2013 at 04:14:08PM -0400, Manuel Ortega wrote: > There is a horrendous bug wrt the 'g~' operator. I've found it on OSX > 10.8.4. Doesn't matter whether it's MacVim 7.4b or Vim 7.4b.18.
> To reproduce: Make a new file with three lines: > ----------------- > a > b > ----------------- > (The middle line is empty, and there's no trailing whitespace after a or > b). Now from the terminal do vim -N -u NONE -U NONE thefile. > With the cursor on the first column of the first line, do: g~ap > Observe that the first line is now "A", and the third line starts with "b". > Now do :redraw!, and observe that the third line suddenly is "B". > That's not how 'ap' is supposed to work, AFAIK. > It gets much worse, though! Now hit 'u' to undo the surprising > capitalization. Observe that "A" returns to "a", but that "B" does NOT > return to 'b'. > So not only is the motion 'ap' messed up, but the undo history is botched > and the original state is unrecoverable with 'u', *and* the change made to > 'b' is for some reason not even shown on the screen right away. Triple > threat. I can confirm the same weirdness happens with version 7.4b.19 in opensuse linux. -- _|_ _ __|_|_ ._ o| |_(_)(_)|_| ||_)||< | -- -- 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 vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.