00:13 <beneroth> DKordic, no worries, I don't consider you difficult.

00:14 <beneroth> its neat

00:14 <DKordic> Thank You. I feel a relief.

00:14 <beneroth> but I don't really have an use for it in my work (I think). And if the need arises, I could implement this as FEXPR in PicoLisp (and have/keep all the other benefits I use PicoLisp for in a project)

00:15 <DKordic> Yes. A matter of style and perspective.

00:16 <beneroth> DKordic, yes, and context of interest/application (application not in the sense of software but in the sense of applying the programming to further some other goal)

00:19 <beneroth> I strongly suspect that for a neat small (KISS) hardware projects (small simple clever components of a possible much larger hardware apparatus) FORTH is very sensible and effective (and PicoLisp not useful at all)

00:20 <beneroth> so far I primarily work with database and web/network applications and for the type of projects I do in that space PicoLisp is just perfect :)

00:23 <DKordic> Have a procedure, OK would be a nice name, that _continues_ information processing and You have a Forth System.

00:24 <DKordic> Exceptions are merely a matter of style.

05:27 <abu[7]> DKordic, thanks for the escape sequence hints. @lib/term.l uses escape sequences for various things, but iirc getting terminal size was not feasible

05:29 <abu[7]> The sequence you use, "\e[18t", where is it documented?

05:29 <abu[7]> And how did you test your 'getSize'?

05:35 <abu[7]> BTW, the easiest is (format (sys "COLUMNS")) etc, but it is not updated after a SIGWINCH singal

05:36 <abu[7]> Same probably with the results of an escape sequence call

05:40 <abu[7]> Besides, as long as even a simple ioctl() does not work, the pil build in not complete