freenode/#clim - IRC Chatlog
Search
18:12:38
jackdaniel
`0: (SB-SYS:MEMORY-FAULT-ERROR # #.(SB-SYS:INT-SAP #X7F190E801680))' – speaking of FFI ;-)
18:21:56
slyrus1
I just deleted FASLs and retried it and con't reproduce it (yet). I'll keep an eye out for it.
3:18:57
beach
When I was in Sweden, I saw posters for some commercial product saying "Who cares about beach in 2018?" I can't remember the product, though.
3:20:27
loke
beach: I think that refers to a popular saying in winter that they are about to get ready for “Beach 2018”, by eating more healthily or workout or whatever. I.e. referring to their upcoming beach body
3:22:24
loke
beach: Anyway, I am really stuck... I spent several hours last night trying to make sense of input histories.
3:22:40
loke
When I thought I figured it out, the behaviour still doesn't fully match expetcattions.
3:26:11
loke
The ACCEPT call on line 179 calls a custom acceptor that calls into one of two separate accceptors depengind on if the first character typed is a :
3:26:59
loke
Now, I have lots of problems all over the place, but I'll just concentrate on one of them right now, because that's the one I have been able to work around:
3:28:09
loke
The call on line 179 ends with :history 'maxima-native-expr. As best as I can tell, that should allow me to browse the input history for all inputs of that type. However, the code as written gives me _NO_ input history.
3:28:45
loke
However, if I change that line to read: :history 'maxima-expression-or-command, then I will get all the history, BUT also including the :-commands, which I do not want.
3:29:45
loke
I've traced internal DREI calls that adds the results to the input history, and I notice each entered command is added to _two_ separate histories. One under the type 'maxima-native-expr and another one user the type 'maxima-expression-or-command
3:30:43
beach
loke: I am having a private conversation with someone. I'll get back to reading this is a little while.