Maxim Kim wrote:
On 27/08/2022 07:56, Charles Campbell wrote:
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?
If you're ok with compiling vim then: (if you're sure v9.0.0000 has no
issues, if it has, choose older version tag)
1. git clone g...@github.com:vim/vim.git
2. git bisect start
3. git bisect bad
4. git bisect good v9.0.0000
build vim, check your plugin if it is bad: `git bisect bad`, if it is
good: `git bisect good`
continue until commit that breaks your plugin is found.
Thank you, All! I'll give this a go when I've got the chance.
Chip Campbell
--
--
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/a4504b87-ab01-73dd-b3a6-974af2cfe8a3%40drchip.org.
