<taleon>
I have always preferred `vi` to `vim`. Meanwhile, I really like `vip`. However, it is not possible for me to install `vip` on all systems. Do any of you have tips on how I can customize my .nexrc to behave similarly to `vip`? The .nexrc I have used so far looks like this: https://termbin.com/gswc
<abu[7]>
Do you mean .vimrc? (I do not know of .nexrc)
<abu[7]>
In fact, for me it was the opposite direction. I had my .viprc since many years, and then built Vip the same way ;)
<taleon>
.nexrc is the config for the original vi. The .vimrc is the config for vim. I was hoping that some of you would use the original vi, since vip is more like vi than vim. :-)
<abu[7]>
Ah, I see
<taleon>
I'll keep an eye on your config. Thanks for sharing. :-)
<abu[7]>
I used standard Vi for many years, but forgot about .nexrc ;)
<taleon>
My .vimrc looks like this. I'll compare it with yours and maybe adjust a few things. https://termbin.com/118w
<abu[7]>
oops, In I had my .viprc since many years" I meant ".vimrc" of course
<abu[7]>
You said "not possible for me to install `vip` on all systems". Which ones for example?
<abu[7]>
No Pil in general?
<abu[7]>
otherwise there is /usr/lib/picolisp/bin/vip out of the box
<taleon>
Unfortunately, it is not always possible to install vip on customer servers. They do not have gcc/llvm installed for security reasons. Often only vi is available there and sometimes also vim.
<abu[7]>
ok, so also not "apt install picolisp"? Then no compiler is needed.
<taleon>
It's not that easy because of certain security guidelines. I maintain many OpenBSD servers.
<abu[7]>
ok
seninha has joined #picolisp
seninha has quit [Remote host closed the connection]