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
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
Hi Charles,
On Fri, Aug 26, 2022 at 9:56 PM Charles Campbell 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
>
Hi,
On Sat, 27 Aug 2022 at 06: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
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
