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 [Ping timeout: 268 seconds]
seninha has joined #picolisp
seninha has quit [Remote host closed the connection]
lispnik has joined #picolisp
chexum has quit [Remote host closed the connection]
chexum has joined #picolisp
lispnik has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
rob_w has joined #picolisp
tankf33der has quit [Quit: the lounge - https://webirc.envs.net]
tankf33der has joined #picolisp
<beneroth> abu[m], what is the best way to find all duplicates uses in a +Ref index? I guess (scan) and compare with the previous key ?
<abu[m]> Yes, scan seems the best (or only?) way
<abu[m]> always looking at the CARs of the keys
<beneroth> yep
<beneroth> good thanks :)
seninha has joined #picolisp
seninha has quit [Remote host closed the connection]
seninha has joined #picolisp
rob_w has quit [Quit: Leaving]
<tankf33der> Again macos compilation issue.
<tankf33der> In the mailing list.
<abu[m]> Yeah :( I have no idea
<tankf33der> I know this issue and understand what to do, but i dont know how to help.
<abu[m]> Difficult to explain?
<tankf33der> I must update wiki steps
<tankf33der> and you could add Makefile.macos file.
<abu[m]> That would be nice!
<tankf33der> Or update Makefile to detect run on macos and modify variables inside
<abu[m]> hmm, I don't want to put that permanently
<tankf33der> i see, this is ok then.
<abu[m]> Thanks! ☺
seninha has quit [Quit: Leaving]
<tankf33der> I have created a repo with custom makefile and share it thru mailing list
<tankf33der> i hope somebody test steps in it
<abu[m]> Cool, good idea!
<abu[m]> Thanks for taking care of the problem!
seninha has joined #picolisp
chexum has quit [Remote host closed the connection]
chexum has joined #picolisp
seninha has quit [Ping timeout: 260 seconds]
<beneroth> awesome, tankf33der! thank you :)
seninha has joined #picolisp
razzy has joined #picolisp
<razzy> i have update on my problem. vip butcher non-utf8 parts of files.
<abu[m]> Not Vip but PicoLisp in general does *not* handle non-UTF8
<abu[m]> You need (in (list "/usr/bin/iconv" "-f" "ISO-8859-15" "-t" "UTF-8" File)
<razzy> i know.
<abu[m]> Yeah, just for the records
<razzy> i was hoping that vip just leaves no-utf8 parts as is. too optimistic :]
<abu[m]> indeed
<abu[m]> Pil cannot read and/or process non-UTF8 characters
<razzy> can you guess how much effort would be to harden pil so it can chew non-utf8 chars?
<abu[m]> How should it do so? What to do if such a character appears in the input stream?
<abu[m]> And then how to know *which* character set to use instead?
<razzy> abu[m]: i am thinking encapsulating all not-utf8. i do not really care which character set it uses, as long as it writes back correct data.
<abu[m]> The best way is to use input and output filters, e.g. with "/usr/bin/iconv" as shown above
<razzy> what if i have files with mixed encoding for different operating systems.
<abu[m]> Then you must parse them
<abu[m]> It is not a matter of operating systems. UTF-8 is the common standard anyway.
<razzy> i have old database, old programs on windows. it is mixed mess. i would rather shoot myself, than parse that headache.
<abu[m]> Have you ever seen a single file with several different character encodings?
<razzy> abu[m]: daily. vi chew it no problem
<abu[m]> I use Vip on encrypted files all the time (my password file). This is also non-UTF8. In this case it works fine
<abu[m]> I do :key <password>
<abu[m]> So the actual editing is in UTF8 then
<razzy> hmmm, i am thinking.
<abu[m]> Anyway, it is not a Vip-problem.You need to extend the PicoLisp I/O primitives
<abu[m]> I think PicoLisp should not be overloaded with such things
<abu[m]> Always call some external conversion tool
<razzy> I/O primitives?
<abu[m]> In case of :key this is /usr/bin/ccrypt
<abu[m]> You could implement some similar mechanism like :key for other data
<razzy> i do not want to burden base pil with edge usecase
<abu[m]> yeah
<razzy> abu[m]: that is good thinking. thx.
razzy has quit [Quit: leaving]
seninha has quit [Remote host closed the connection]
seninha has joined #picolisp
theruran has quit [Quit: Connection closed for inactivity]