<m_mans>
Regenaxer: > I'm very reluctant to change this
<m_mans>
np, I'd like to build the whole picture of this issue first. Maybe we can workaround this just by changing something in application code or in CSS
<m_mans>
maybe using ".field" CSS selector was wrong decision (it was done before I came to the company). We can customize CSS just for all 'input's and 'select's etc
abel-normand has joined #picolisp
abel-normand has quit [Remote host closed the connection]
abel-normand has joined #picolisp
<Regenaxer>
Hi m_mans
<Regenaxer>
Not sure, but ".field" seems to be the "unexpected" issue here, yes
<Regenaxer>
I'm glad if we can investigate this more
<Regenaxer>
For now, I think it is OK if picoLisp-17.12 is released in the current state
<m_mans>
of course, np
<aw->
hi all
<aw->
is there a quick way to (pp) the contents of a (load)'ed file?
<aw->
without re-loading it
alexshendi has quit [Ping timeout: 248 seconds]
abel-normand has quit [Quit: ERC (IRC client for Emacs 25.3.1)]
<Regenaxer>
Hi aw-
<Regenaxer>
(in "file.l" (while (read) (pretty @) (prinl)))
<Regenaxer>
Not tried
<aw->
hi Regenaxer
<aw->
how can i do that if it's already loaded?
<Regenaxer>
What is different if it is loaded?
<aw->
can't perform a read on the file more than once
<aw->
ex: file is removed after (load)
<Regenaxer>
What use case do you have?
<aw->
it's just hypothetical
<aw->
i want to know how to see what symbols were created after (load)
<Regenaxer>
I see
<Regenaxer>
then do (all) before and after loading
<Regenaxer>
and 'diff'
<aw->
(all) ! perfect
<aw->
that's what i was looking for
<Regenaxer>
:)
<aw->
thank you!
<aw->
actually i was going to use md5sum to diff two picolisp files, but (diff) would be easier haha
<Regenaxer>
:)
<aw->
and this is better because I don't need them to be exact matches.. only the lists need to contain the same contents, but ordering doesn't matter
<Regenaxer>
So you read them both into lists, and sort and compare these?
<aw->
right now yes
<aw->
but with (diff) i don't need to sort
<Regenaxer>
If you consider only the new symbols, yes, and not the actual definitions
<aw->
right
<m_mans>
aw-: are you working on some PL project?
<aw->
m_mans: yes, always
<aw->
hahahaaa
<m_mans>
:)
<aw->
now i'm actually rewriting a terrible bash script, in PicoLisp
<m_mans>
that's good.
<Regenaxer>
picoLisp-17.12 is out!
<aw->
great!
<aw->
what's different?
<Regenaxer>
Arm64 support for example
<aw->
Christmas release, almost 1MB .tgz file
<aw->
:D
<Regenaxer>
Must ask the Debian maintainer to support it
<aw->
oh yeah.. i'm already using the arm64 release
<aw->
works fine
<Regenaxer>
Good to hear
<aw->
debian stretch arm64
<Regenaxer>
I have not tested much, only on qemu
<Regenaxer>
So we can consider it safe
<Regenaxer>
:)
<aw->
yes i've tested most of my libs, even with (native) and they work as well
<Regenaxer>
cool
<aw->
oh actually, one thing doesn't work but that might be an arm64 thing
<aw->
(native "@" "prctl" NIL 15 "my-app")
<m_mans>
Regenaxer: congratulations!
<Regenaxer>
What happens?
<aw->
oh wait, it works
<aw->
never mind
<Regenaxer>
m_mans, thanks!
<aw->
i can see it with ps -e
<Regenaxer>
OK :)
<aw->
Regenaxer: thanks!
<m_mans>
btw, do you often use 'dbs+?
<Regenaxer>
No, it was only once in fact
<aw->
m_mans: i don't, actually never have
<m_mans>
and you, Regenaxer? :)
<Regenaxer>
It may not be terribly useful
<Regenaxer>
only once, in the Smapper project
<m_mans>
siimply I'm confused with it's first parameter (num)
<m_mans>
it seems 'dbs+ can only append to the end of *Dbs
<Regenaxer>
yes, this is the purpose
<Regenaxer>
to extend a project without modifying the base system
<Regenaxer>
it was used for the remote DBs
<m_mans>
so, why we need that parameter? Is it recorded also to some another place (class definition maybe)?
<Regenaxer>
You mean we could use the actual length?
<Regenaxer>
I think this is not good, because then the base system cannot be easily extended later
m_mans has quit [Ping timeout: 240 seconds]
m_mans has joined #picolisp
alexshendi has joined #picolisp
<m_mans>
sorry, network issues. Last line I've seen: I think this is not good, because then the base system cannot be easily extended later
<Regenaxer>
yes, this was the last one
<m_mans>
ok. It seems I just need to read more info about dbs+ and extending system
<Regenaxer>
I find only this single case, and don't remember the details atm:
<Regenaxer>
(dbs+ (if *Minimal 11 19)
<m_mans>
maybe I'll find anything in ML and chat logs
<Regenaxer>
I don't think so. It was never an issue I think
<Regenaxer>
Where do you need it?
<m_mans>
We are building system that (I hope) will grow later
<Regenaxer>
ok, yes, so dbs+ is useful here
<m_mans>
So I have to learn how to manage base classes and additional modules
<Regenaxer>
I think there is nothing special to learn for you
<Regenaxer>
It is more how you modulize the total project
<m_mans>
Or I shouldn't worry yet?
<Regenaxer>
exactly :)
<m_mans>
at the moment although we define some additional DB classes in modules' files, but we have single (dbs) expression in er.l
<Regenaxer>
This is enough I think, easier to maintain
<Regenaxer>
You can easily change to dbs+ later if needed
<m_mans>
good
<m_mans>
thanks
<aw->
finally added picolisp support to gtksourceview (Pluma/Gedit)
<m_mans>
aw-: could you explain more? And maybe share it?
<m_mans>
also multiline comments support?
<aw->
multiline comments?
<aw->
i've never seen those in pil
<Regenaxer>
I use them a lot, though mostly temporarily, they don't remain in final sources