beneroth changed the topic of #picolisp to: PicoLisp language | The scalpel of software development | Channel Log: https://libera.irclog.whitequark.org/picolisp | Check www.picolisp.com for more information
seninha has quit [Quit: Leaving]
<abu[7]> Strange. Why is a touch required? base.bc does not exist after a clone, but base.ll does, so the make should build the rest.
<abu[7]> Hmm. Perhaps is it because repos do not preserve timestamps? Then the *.l files may be newer and it tries to build base.ll, which fails if no bin/picolisp exists yet
<abu[7]> This is the reason why I hate and don't use repos like git
<abu[7]> They discard the important file meta data
gahr has quit [Remote host closed the connection]
gahr has joined #picolisp
<taleon> I'm not sure if this is necessary. Under `$HOME/.../pil21/bin/` are some tools, like `picolisp`, which point to `#!/usr/bin/picolisp` in the shebang. If I have built PicoLisp in my `$HOME/.../`, do I have to change all the shebangs manually to my `$HOME/.../pil21/`?
<tankf33der> i always add /root/pil21 to PATH
<tankf33der> always run pil for code
<taleon> Yes, that's how I did it too. I just wasn't sure because there are other tools under bin.
<tankf33der> yea
<taleon> Anyway, pil works fine with repl under emacs. I only had to deactivate the eldoc because no docs were found.
<tankf33der> i always code in micro editor and call code via key-bindings
<taleon> Micro sounds interesting. I didn't know this editor until now. After 30 years I switched from vim to emacs, although I still mostly use the old vi for editing.
<taleon> Do you have any documentation regarding micro and PicoLisp in your repo? :-)
<taleon> Hm... `Fatal: Micro could not initialize a Screen.`
<tankf33der> yea, openbsd.
<tankf33der> btw, works on freebsd
<taleon> Thanks for the configs. There is an official port from micro to OpenBSD. Therefore it should actually work.
<tankf33der> check config for *.l files
<tankf33der> and how i post code to pb1n.de
<tankf33der> written on picolisp
<taleon> Thanks, I'll check that later.
<abu[7]> back
<abu[7]> I did not follow. taleon, is the 'pil' question solved?
<abu[7]> pil21/pil is used as it is
<abu[7]> pil21/bin/pil is for globall install, so it needs the right hashbang, yes
<abu[7]> But I think Unix does not accept variables like $HOME in the hashbang
<abu[7]> (not sure, at least it used to be so in traditional Unixes)
<taleon> Perhaps you could use an env(1) and define it in ~/.profile or similar. For example `export PLPATH=$HOME/.../pil21` and then in the shebang `#!/usr/bin/env pil`. Or something like that. PicoLisp then checks whether $PLPATH is set.
<abu[7]> Too complicated I think. For PicoLisp the hashbang is a comment and thus ignored
<taleon> abu[7]: Yes, pil works fine, as far as I can tell.
<abu[7]> great :)
<taleon> Ok :)
seninha has joined #picolisp
seninha has quit [Remote host closed the connection]
seninha has joined #picolisp
<abu[7]> So everything works under OpenBSD? How about the shared libs? E.g.
<abu[7]> : (ext:Snx "taleon")
<abu[7]> -> "TLN"
<taleon> abu[7]: https://rt.fm/tmp/pl.png
<taleon> Looks good to me as a beginner. Time will tell ;-)
<abu[7]> Yes, all correct
<taleon> Is there an option in viprc to change the color of the comments for vip? I'm not a fan of colors in editors. I would like to keep the code in black and the comments in gray.
<abu[7]> The colors are hard-coded. But you could change them with : (vi 'vip~addLine)
<abu[7]> ... (attr CYAN) ...
<taleon> Thank you. If I set the color to `GRAY` or `GREY`, it turns black. If I set the color to `YELLOW`, it becomes gray, just as I want it, even if I don't know why. :-)
<taleon> Are the colors of the terminal evaluated? I may have changed the colors here.
<abu[7]> You can find the colors if you press Shift-K on e.g. CYAN
<abu[7]> it goes to @lib/term.l
<taleon> Hm no, the colors of my terminal look ok for yellow: `*.color3:#b58900` and `*.color11:#839496`
<taleon> Ah ok thank you.
<abu[7]> You see that currently only a few colors are there
<taleon> I see. Slowly it makes more sense.
<abu[7]> But your idea with viprc is not bad
<abu[7]> you can redefine 'CYAN' there ;)
<abu[7]> I put (setq CYAN "0;31") and comments are red :)
<abu[7]> A bit ugly though
<taleon> How are the colors calculated? I usually know this in rgb notation.
<abu[7]> These are standard terminal escape sequences, so not normal color codes
<taleon> Ah thank you.
<abu[7]> This is the full list: http://pb1n.de/?8677bd
<taleon> Great, thank you. Immediately saved in an .org file. :-)
<abu[7]> 👍
<abu[7]> taleon: I'm very glad that you don't like colors in editors. Exactly like me.
<abu[7]> Many people asked here for syntax highlighting :(
gahr has quit [Remote host closed the connection]
<tankf33der> Colors
<abu[7]> Yes, escape sequences
<abu[7]> but somehow different codes. No idea.
<abu[7]> BTW, (setq CYAN ...) in viprc is also not a bad idea because 'CYAN' is private in the 'vip' namespace here, and won't conflict if @lib/term.l is loaded also in the application code
bjorkintosh has joined #picolisp
bjorkint0sh has quit [Ping timeout: 245 seconds]
Iacob has quit [Ping timeout: 268 seconds]
<fbytez> How can I output a number as 64 bit binary even if it's a small value like "10"?
<abu[7]> (pad 64 (bin 2))
<fbytez> Sorry, I mean the actual raw binary data, not a text representation.
<abu[7]> (wr 0 0 0 0 0 0 0 2)
<abu[7]> But this depends on the endianess
<abu[7]> (as always for I/O)
<fbytez> Righto. Cheers.
<abu[7]> :)
Iacob has joined #picolisp
pablo_escoberg has quit [Quit: Client closed]
pablo_escoberg has joined #picolisp
bjorkintosh has quit [Quit: Leaving]