<anddam>
taleon: can't you build a binary package?
<taleon>
anddam: Yes, this works and I have already done this on my own systems. Nevertheless, I wanted to avoid using external binaries on customer servers. This also has something to do with the liability issue, in case that should ever come up. It's a different story with configs. I often use my own .nexrc or .vimrc. I'm not interested in using vip or pil on other people's systems, but rather in the user
<taleon>
experience and training my muscle memory. :-)
<taleon>
I may have been a little unclear yesterday. I was more interested in configs for vi or vim to reproduce the vip user experience ;-)
<taleon>
Unfortunately I get some error messages and vip aborts with an error message when starting. pil starts without problems but pil + also gives an error message: https://termbin.com/yd2q
<taleon>
The pil21 directory is exported in $PATH. Does anyone have an idea?
<abu[7]>
This is the same problem as we had with ta
<abu[7]>
tankf33der here yesterday
<abu[7]>
i.e. the dynamically loaded library format
<abu[7]>
Not sure what it exactly is
<anddam>
taleon: out of curiosity can you try iTerm2?
<abu[7]>
Perhaps you can find out more?
<abu[7]>
the terminal size is probably a related problem
<taleon>
My PicoLisp experience is limited. But I'll see if I can find a solution.
<abu[7]>
ioctl() call via 'native', i.e. a shared lib call
<abu[7]>
ok, great!
<abu[7]>
I'm on the road today, so my attention here is a bit limited
<taleon>
The terminal size message also appears when I use alternative terminals.
<taleon>
No problem. I'm not in a hurry, as I only use macos very rarely. Just wanted to try it out. I'll play around with it a bit and see if I can find a solution.