11:12:36nyefSudoku with irregularly-shaped subregions, huh?
11:13:43nyefI play a variant with irregularly-shaped subregions and instead of the grid being seeded with numbers, there are *more* subregions of varying sizes marked with the total of all the digits inside.
11:54:57nyefUnfortunately, Linux tends to be completely useless at getting files off an Android device, or I'd be able to share a screenshot. /-:
11:59:44beachflip214: Thanks. I don't think I will study it right away. I need to get some real work done today.
12:08:35flip214nyef: use ADB... or the gnome-virtual-filesystem and mtp... or let android display its storage as a block device...
12:11:03nyefflip214: mtp has, in my experience, never worked right. The block device thing hasn't been available since mtp came in. And I don't have an android devkit installed.
12:27:01flip214well, bluetooth? wlan and HTTP upload? do you have a terminal app and bash, so that "cat file > /dev/tcp/other-host/port" would do a simple TCP transfer?
12:53:28beachThat REPL is very incomplete. You can't expect to run arbitrary code with it. But you can try out simple things. Loading a file such as sbcl.lisp very likely will not work, and it doesn't make much sense either.
12:56:59beachOK, let me ask you this instead: when you say you want to compile and run Cleavir, what do you expect it to produce when it runs?
12:58:50reg_I am behind a proxy and I cannot install quicklisp
12:58:59reg_will have to repeat the whole process this evening
12:59:16beachSince Cleavir is a "compiler framework", i.e., a library that needs a fairly large amount of customization from the implementation running it, it can't really be "run" independently of such an implementation. Perhaps the best solution is to use Clasp. Then you get to use Cleavir with each interaction.
12:59:17reg_I expect to be able to execute this code
14:02:00nyefOh, I'm not even going to try to deny that it's useful, I'm just saying that it's badly out-of-scope and not _discoverable_.
14:02:31nyefOh, and that it potentially conflicts with something that could happen in the filesystem.
14:02:58nyefUsing something like UNC filespecs would have been saner.
14:10:33nyef(Except, of course, some systems already use UNC filespecs, so it'd have to be something _else_ that doesn't collide the filepath namespace.)