You are not logged in.
So today pacman suggest this package to replace vi ? https://archlinux.org/packages/extra/any/ex-vi-compat/
I'm curious why is that the case and decision to do so ? Seems also the old vi package is no longer in the extra repos, and in the AUR doing a quick search.
Last edited by Succulent of your garden (2026-01-26 17:36:12)
str( @soyg ) == str( @potplant ) btw!
Offline
from https://gitlab.archlinux.org/archlinux/ … da99b3030d
Add package as replacement for the "traditional vi", which is unmaintained and no longer builds.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Thanks for the info ^^
str( @soyg ) == str( @potplant ) btw!
Offline
Hmm, it builds fine for me if I add
CFLAGS=-std=gnu90before the call to make in the PKGBUILD. If there's no plan to re-add it to the official repositories, I would consider maintaining an AUR package for it, except the main source tar file comes from somewere on sources.archlinux.org, and I'm not sure if that's stable enough to base an AUR package on, or if that file is likely to be deleted soon as well if the official package is no longer supported?
Vim is nice and all, but for really slow terminals, ancient vi is way faster. I'm sure that's a very niche use case though, and not reason enough to warrant a official package.
Offline
Vim is nice and all, but for really slow terminals, ancient vi is way faster. I'm sure that's a very niche use case though, and not reason enough to warrant a official package.
No, there are many places of the world esp south america that still have slow network performance. Even where I live it was very slow until about 8 years ago. But I have had bad connection to VPS more recently than that like when it was getting flooded and I had to run everything under a tmux because otherwise the command would be killed when the shell randomly dropped out. But I think I have only typed vi instead of vim once or twice its not really on the top of my mind but that's just me maybe.
I do remember that back in the day the linux on the dedicated servers always had vi preinstalled, not vim, because you had to switch out of insert mode to move the cursor, which was a bit annoying, but I suppose there was a reason for it, more reliable or uses less libraries that can get borked or smaller filesize or something maybe.
but it looks like someone already made an AUR of heirloom-ex-vi-git maybe that is similar, but couldn't you just take the sources.archlinux.org content and put it on a github and then pull from github in the pkgbuild?
I currently use fish terminal so I don't personally have any concern with terminal speed these days anymore heh
Offline
The last release of vi was in 2005.
Even the fork used in heirloom-ex-vi-git hasn't had a release since 2017 or commits since may 2022 .
Unless someone takes over and revives vi , vi is unmaintained.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
but it looks like someone already made an AUR of heirloom-ex-vi-git
Ah, perfect. I couldn't find that one. Thank you.
It looks like that version also contains most of the patches that the old Arch package also applied to the Sourceforge source, plus a few other improvements, and the AUR package maintainer fixed the CFLAGS yesterday as well so it builds just fine now.
Offline
Busybox still provides a minimal vi implementation. For such limited / minimal systems busybox seems like a no-brainer to me.
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline