On 2026-01-29, Eli Schwartz wrote: > On 1/28/26 9:37 AM, Anna (cybertailor) Vyalkova wrote: > As I said prior, I don't think this is a good idea, especially given > > > "Native Vim packages make everything a lot more simple, so let's use them." > > > is wrong because it is not, in fact, more simple. It lacks commit > message rationale, and I disputed the rationale you gave in IRC to which > you even replied "I sort of agree".
They solve a real widespread problem of file collisions between vim plugins: https://bugs.gentoo.org/buglist.cgi?list_id=7630989&query_format=advanced&short_desc=app-vim%20file%20collision&short_desc_type=allwordssubstr You can't really detect them unless you install every vim plugin on your system. > The weird after/syntax bits should simply be removed without > replacement. By the way, this workaround was added by me for EAPI 8 in attempts to address the aforementioned problem. https://marc.info/?l=gentoo-dev&m=164968045410908&w=2 > Adding stripped-down perl implementations of vim seems out > of place (I have a planned simplification for helptags that will help > here). Indeed, this script is simple enough so that having multiple implementations of it is justified. Looking forward to it. > vimproved has a vastly simpler neovim support update I'd prefer > to look at (added to cc). Where can I see it?
