On Fri, 12 Jun 2026 19:11:23 +0200 Matthias Geiger
<[email protected]> wrote:
On Fri, 12 Jun 2026 18:56, Amin Bandali <[email protected]> wrote:
>Hello,
>
>Matthias Geiger wrote:
>
>> [... 21 lines elided]
>> Hi,
>>
>> I just asked jamessan if they are ok with having it
>> team-maintained. best,
>>
>> werdahias
>
>Thanks. Any word from jamessan about this?
>
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
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.
