Hi Charles, On Fri, Aug 26, 2022 at 9:56 PM Charles Campbell <campb...@drchip.org> wrote: > > Hello: > > I've got a plugin that I wrote years ago that I only just noticed is > misbehaving; ie. it used to work properly but it no longer does. > > So, I thought what I'd like to do is to get vim 9.0 back (with no > patches) and see if that worked. Then, if the plugin continues to > misbehave, then I'd like to get vim 8.0. Once I have a version of vim > where the plugin works I'd like to use git bisect to find the > problematic patch. I realize that I'd have to learn more git. So, how to > get vim 9.0, vim 8.0?
You can use the following commands to checkout the Vim 9.0 and the Vim 8.0 versions: $ git checkout tags/v9.0.0000 $ git checkout tags/v8.0.0000 You can then use the "git bisect start", "git bisect bad" and "git bisect good" commands to find the problematic patch. - Yegappan > > I've traced the problem to visual mode stuff. Essentially, use visual > mode to select some text, delete and move it to the end of file, operate > on it, and move it back. When I do the commands that the plugin issues > by hand, things work correctly. When the plugin does those same > commands, instead of putting back the column of text vim forgets to use > visual-block mode style insert (and visualmode() is still returning a > ctrl-v before&after). > -- -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/CAAW7x7nFKAFr9HmRC3z6W9NHB8osNNGdBaaENk4QWayengAy-g%40mail.gmail.com.
