You are not logged in.
Pages: 1
So I already have gvim so vi seems a bit redundant. I'd rather build my own package and have vi be a symlink to vim. vi is a base package, though. Is there any reason not to do this?
Last edited by AaronBP (2012-08-19 21:10:44)
Offline
Can just use an alias in ~/.bashrc, e.g.:
alias vi=/usr/bin/vim
alias v=/usr/bin/vim
alias gvi=/usr/bin/gvim
Offline
I have a symlink in /usr/local/bin/vi pointing to /usr/bin/vim. If you really need to make the package, make sure you solve the conflict with the vi package in the PKGBUILD.
Offline
I have a symlink in /usr/local/bin/vi pointing to /usr/bin/vim. If you really need to make the package, make sure you solve the conflict with the vi package in the PKGBUILD.
You know, that sounds like a much better idea than trying to maintain my own version of Arch's crazy vim package. Thanks!
Offline
You can remove core/vi if you want to. I assume it's in the "base" group so that you always have an editor after installing. It's not actually *required* by anything (at least, not in the official repos).
If you do that though, you might want to use abs to repackage (g)vim so it provides view and ex, (and vi too, if you want).
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
Pages: 1