13:40:16_deaththere, at the edge of the world, as chaos disperses bits throughout, lay the petrified common lisp hyperspec, ready to pronounce your implementation nonconforming
13:41:01grubletbut it has a lisp, so it can't pronounce things very well
13:58:07krator44too bad that the spec is proprietary..
13:58:23krator44that's actually a huge disadvantage of the language
14:01:30krator44in some.. attempt to stay relevant they keep the copyright on that
1:03:25emaczenI've had this problem for like 3 weeks -- I've been just "accepting" 1: [ACCEPT] Continue, treating compiling #<CL-SOURCE-FILE "parenscript" "src" "lib" "ps-loop"> as having been successful. -- from the restart
1:03:48whomanhmm, it works and loaded from QL perfectly (and quickly!)
1:05:23emaczenwhoman: the only other thing I can think of is looking at my *readtable*
1:05:43emaczenupdate-dist "quicklisp" does what exactly though?
1:06:13whomanupdates all the things. not sure if that is right command, but that is what i can think of because i have updated recently (because so has QL)
1:06:33emaczenwhoman: now it fails to compile Usocket...
1:06:40emaczenI'm going to restart and try again...
1:07:12whomanyou may try to delete all the parenscript stuff in ~/quicklisp/ ? that is one thing i would do if it were happening to me
1:07:17emaczennope, still fails to compile parenscript
1:13:23emaczenwhoman: I still get Reader error on #<BASIC-FILE-CHARACTER-INPUT-STREAM ("/Users/thutmose/quicklisp/dists/quicklisp/software/Parenscript-2.6/src/lib/ps-loop.lisp"/34 UTF-8) #x30200499554D>, near position 8980, within "(:map) '{}))))