9:48:36beacholeo: It is usually a bad idea to ask a question like that. Even if someone does, they might not want to let you know until they know why you asked that question.
9:49:11beacholeo: I don't personally use it, but why do you want to know?
9:50:32shkaoleo: it seems that it is all about mezzano this days
9:55:04Posterdatiplease, how can I convert a foreign pointer to an uint64??
9:58:48oleoshka: well i tried to use it, i got it from 2 different github sources and i can create images with both, when i try to use the images only one works tho....and it seems somehow crippled anyway......with the other i get an error with grub telling me the image is too big for the bios to handle it....
9:59:31shkawell, i never tried to run those physical machine
10:00:22beachI have run Movitz on real hardware, but nothing recent.
10:00:43oleoshka: i solved the nickname issue via replacing bt: with binary-types: with sed but the movitz-browser/browser.lisp file uses the same bt: too for bordeauxh-threads (so it's inconsistent across files, so you have to manually check)
10:02:10oleoshka: i tried to use the bare images with no luck when i put the grub images onto the other then i can start both via qemu...but like i said one boots and seems crippled (there's no movitz-brower package for exmaple) and the other is unbootable even tho it appears in the grub menu.....
10:02:50oleoi tried to even mount -o loop some of the images but without luck either.....
10:02:52beacholeo: frodef, the author of Movitz, occasionally comes here. He was here a few weeks ago. You might drop him a note.
10:03:39oleoi peeked into the images to see how they are layered with fdisk -l and trying the offset=bla when mounting via -o loop but it doesn't work either....
10:04:41oleobeach: the first partition is 1 T in both images.... so i don't see where the issue stems from....
10:05:46oleobeach: thank you.....maybe it's an issue with 32bit instruction set on a 64bit machine too....
10:07:10oleoshka: welp, i just build mezzano too.....
13:13:08beachSpeaking of which, I decided to write down my ideas for improved Common Lisp standard a bit more concretely: https://github.com/robert-strandh/Well-Specified-Common-Lisp
13:14:27beachACTION is guessing that the first several complaints will be about the planned markup language, and that these complaints will each be associated with a different suggestion for an alternative.
13:29:49SAL9000ebrasca: okay, bare emacs vs emacs+evil-mode
13:30:08shkaSAL9000: nah, this won't cut it for me
13:30:27SAL9000in that case I'll second ebrasca's recommendation of org-mode
13:30:33SAL9000heck, I used it to write my Honours thesis
13:31:18shkai need something that i can use to blend doc strings, drawnings, tables, and paragraphs
13:31:44beachebrasca: By "Satisfied?" I meant "Are you convinced that I am right that Common Lisp is not sufficiently well specified, thereby justifying the need for something like WSCL?".
13:32:33shkai almost think that i should start cloning scribble in CL