#1138876 ITP: vim-classic -- stable, long-term support fork of Vim

#1138876#5
Date:
2026-06-05 03:37:06 UTC
From:
To:
* Package name    : vim-classic
  Version         : 8.3.0
  Upstream Contact: https://lists.sr.ht/~sircmpwn/vim-classic-discuss
* URL             : https://vim-classic.org
* License         : Vim
  Programming Lang: C
  Description     : stable, long-term support fork of Vim

Vim Classic is a fork of Vim 8.x for long-term maintenance,
providing a stable, dependable editor, maintained without the
assistance of generative AI tools.

They just had their first release, 8.3.0, based on Vim 8.2.0148.
https://vim-classic.org/news/vim-8.3-released.html

I'd like to package and maintain vim-classic as part of the Vim team
along with Vim itself and Neovim, if the Vim team folks would be open
to it.

#1138876#10
Date:
2026-06-06 15:42:26 UTC
From:
To:
Hi,

I just asked jamessan if they are ok with having it team-maintained.

best,

werdahias

#1138876#15
Date:
2026-06-12 16:56:19 UTC
From:
To:
Hello,

Matthias Geiger wrote:

Thanks.  Any word from jamessan about this?

#1138876#20
Date:
2026-06-12 17:11:23 UTC
From:
To:
17:27 < werdahias> jamessan: any objection to maintaining vim-classic in
the team?
00:52 < jamessan> I don't think it's worth packaging, but I'm not going
to stop anyone from doing so.
01:05 < werdahias> ack

I created vim-team/vim-classic and granted you access; note that we use
gbp with debian/latest and upstream/latest (no pristine-tar).

best,

werdahias

#1138876#25
Date:
2026-08-27 19:58:43 UTC
From:
To:
On Fri, 12 Jun 2026 19:11:23 +0200 Matthias Geiger <werdahias@riseup.net> wrote:

Not trying to derail this ITP, but I'm personally trying to decide
between evi and vim-classic. I am curious why folks are choosing to
package vim-classic versus evi. Both are forks that eschew AI, while evi
is based on vim 9.1.x and vim-classic is based on vim 8.2.x. I don't do
any vim scripting, so I don't have insight into the
problems/improvements that were introduced with the vimscript9 stuff.