freenode/#lisp - IRC Chatlog
Search
9:48:36
beach
oleo: 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:58:48
oleo
shka: 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....
10:00:43
oleo
shka: 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:10
oleo
shka: 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:52
beach
oleo: frodef, the author of Movitz, occasionally comes here. He was here a few weeks ago. You might drop him a note.
10:03:39
oleo
i 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:41
oleo
beach: the first partition is 1 T in both images.... so i don't see where the issue stems from....
10:05:46
oleo
beach: thank you.....maybe it's an issue with 32bit instruction set on a 64bit machine too....
13:13:08
beach
Speaking 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:27
beach
ACTION 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:16:45
SAL9000
only a turing-complete markup language can represent the full power of CL, after all
13:22:15
specbot
The ``Arguments and Values'' Section of a Dictionary Entry: http://www.lispworks.com/reference/HyperSpec/Body/01_ddc.htm
13:22:28
beach
"Except as explicitly specified otherwise, the consequences are undefined if these type restrictions are violated."
13:23:29
shka
beach: I really wish we could have something to write and manipulate markup directly from CL
13:24:03
shka
so it would be more like: make objects that represent paragraphs, join together, output to pdf
13:25:12
SAL9000
shka: why not? I always end up missing the full power of LaTeX when I'm writing, say, HTML
13:26:01
shka
SAL9000: honestly, I am just really disappointed by current status of lisp ecosystem when it comes to document preparation tools
13:26:38
SAL9000
there's a half-dozen different docstring-extraction things I've seen in use already
13:28:55
beach
AND... here we are again in the eternal debate of the advantages over one markup language over another.
13:31:18
shka
i need something that i can use to blend doc strings, drawnings, tables, and paragraphs
13:31:44
beach
ebrasca: 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:34:31
beach
ebrasca: If at some point you take the time to read the description of WSCL, you will see how totally different it is from cl21.
13:35:10
beach
ebrasca: For one thing, I mainly plan to specify what most Common Lisp implementations already do.
13:36:31
beach
ebrasca: But thanks. Once I get things started, I'll let you and everyone else know what there is to be done.
13:37:06
shka
ebrasca: phoe put this thing together so we can have independent documentation from hyper spec
13:37:30
beach
ebrasca: CLUS is an improved specification of Common Lisp, whereas WSCL is a specification of an improved Common Lisp.
14:04:17
loke
The biggest event I'm part of here is the Emacs Meetup. Usually finds around 10 participants.
14:25:08
beach
Videos typically take some time before being posted. It is all done by volunteers, after all. And those people tend to be the same ones that are busy with tons of other stuff.
14:25:36
beach
If you haven't been to ELS before, you can start with videos from previous conferences.
16:06:31
Posterdati
please help, how can I match a lisp integer type with the corresponding foreign type? Thanks!
16:10:02
Bicyclidine
hm, i suppose you could have a fixed ctype->lisptype map (like :uint8 is (unsigned-byte 8)) and then to do the other way, find the smallest mapped type that a given lisp type is a subtype of
16:15:25
pjb
Posterdati: you could define the foreign types as lisp types, and then use subtypep to match the lisp types to them.
17:54:40
oystewh
is there an idiom for finding the index for which an element in an array is maximized?
18:07:16
beach
It might do two traversals. If you want to avoid that, I think you have to do it "manually", by traversing the sequence and assigning to an index every time you find a larger element.
18:08:47
beach
(let ((index 0) (max (aref array 0))) (loop for i from 1 below (length array) when (> (aref array i) max) do (setf index i) (setf max (aref array i)) finally (return index))) something like that.
18:09:47
beach
The performance issue is typically not the traversal per se, but the application of the :KEY function which is often non-trivial.
19:39:51
Bicyclidine
changing the element type of a stream is impossible, as far as i know, but you can bind a stream with a different element-type to those variables
19:42:17
Bicyclidine
(let ((*standard-input* (open wherever :element-type '(unsigned-byte 60)))) ...) is fine