how to get old versions of vim

[Charles Campbell]

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?

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).

Chip Campbell

[François Ingelrest]

Hi,

On Sat, 27 Aug 2022 at 06:56, Charles Campbell <camp...@drchip.org> 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?

I've never used git bisect myself, but AFAICT it will check out the
revisions by itself each time you tell it whether the current revision
is good or bad. As to find the initial good/bad commits, you can
simply use e.g., "git checkout v9.0.0000". The command "git tag" will
tell you all the tags you can check out.

[Yegappan Lakshmanan]

Hi Charles,

On Fri, Aug 26, 2022 at 9:56 PM Charles Campbell <camp...@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

[Maxim Kim]

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.

[Charles Campbell]

Thank you, All! I'll give this a go when I've got the chance.
Chip Campbell