2016-08-24T01:35:59Z ddp joined #ccl 2016-08-24T02:04:05Z ddp quit (Quit: ddp) 2016-08-24T02:54:48Z pierpa quit (Ping timeout: 250 seconds) 2016-08-24T05:31:19Z rme quit (Quit: rme) 2016-08-24T06:47:26Z edgar-rft quit (Quit: edgar-rft) 2016-08-24T07:45:06Z milanj joined #ccl 2016-08-24T08:21:46Z milanj quit (Quit: This computer has gone to sleep) 2016-08-24T08:35:08Z StephanLahl joined #ccl 2016-08-24T08:44:38Z ddp joined #ccl 2016-08-24T08:46:02Z edgar-rft joined #ccl 2016-08-24T08:47:58Z ddp quit (Client Quit) 2016-08-24T10:40:51Z milanj joined #ccl 2016-08-24T12:57:03Z pierpa joined #ccl 2016-08-24T13:14:59Z rme joined #ccl 2016-08-24T13:16:48Z PuffTheMagic joined #ccl 2016-08-24T13:17:34Z PuffTheMagic: when at a ccl prompt, if you type :a and hit enter it just hangs there... how to you break out of this without killing ccl? 2016-08-24T13:59:59Z pierpa: have you tried ctrl-c ? 2016-08-24T14:00:44Z PuffTheMagic: yeah, that would normally work when I was on osx/linux but I am playing on windows right now 2016-08-24T14:00:56Z PuffTheMagic: not sure if it is my shell or something different about the windows lisp binary 2016-08-24T14:01:18Z pierpa: first typing :a at the prompt shouldn't hang. You must not be at a normal prompt. 2016-08-24T14:01:30Z pierpa: second, ctrl-c work on windows. 2016-08-24T14:02:30Z pierpa: so, what did you do before getting at this prompt? 2016-08-24T14:03:01Z PuffTheMagic: i dont mean its hung has in crashed, I just cant seem to escape out of this stuck situation without killing the process 2016-08-24T14:03:22Z pierpa: ok. But what is the situation? 2016-08-24T14:04:28Z pierpa: at a top-level prompt, I get: Unknown command :A 2016-08-24T14:04:45Z pierpa: And that's it. No situation to get out from 2016-08-24T14:05:55Z PuffTheMagic: ahh you know what, its probably a thread/socket that is stuck when I cntrl-c to kill it 2016-08-24T14:06:03Z pierpa: hmmm 2016-08-24T14:06:15Z PuffTheMagic: because if I do :a on a fresh instance I get the unknown command :a 2016-08-24T14:07:08Z PuffTheMagic: i think this is a conemu/powershell issue, i hate windows 2016-08-24T14:07:33Z pierpa: hmmm 2016-08-24T14:07:52Z pierpa: I'd search the culprit somewhere else 2016-08-24T14:13:49Z pmicoss joined #ccl 2016-08-24T14:45:59Z ddp joined #ccl 2016-08-24T14:46:19Z ddp quit (Client Quit) 2016-08-24T15:27:32Z edgar-rft quit (Quit: edgar-rft) 2016-08-24T15:48:14Z pmicoss quit (Read error: Connection reset by peer) 2016-08-24T15:54:26Z pbgc joined #ccl 2016-08-24T17:22:33Z rumbler31 joined #ccl 2016-08-24T17:28:51Z Xach: Hmm, I'm having trouble running a program with ccl:run-program - getting error status 2 no matter what I try. My current guess it is that it has something to do with the spaces in the path to the .exe file. 2016-08-24T17:30:02Z Xach: Oh, this is on Windows. 2016-08-24T17:30:05Z rme: Xach: On Windows, then? 2016-08-24T17:30:07Z rme: Right. 2016-08-24T17:32:20Z Xach: I checked the manual for the string "space" in the run-program section but didn't find it 2016-08-24T17:33:37Z rme: I'm just guessing here, but maybe it would give you a hint. There's a function called ccl::make-windows-command-line. It is supposed to escape various stuff according to Windows conventions, but I suppose it could be getting something wrong. I think there's a run-program type of function in uiop that might be more careful about the escaping, but I'm not sure. 2016-08-24T17:36:40Z Xach: Hmm, ok, I'll look into it. 2016-08-24T17:55:15Z pipping: Xach: users of run-program on windows are rare. if uiop:run-program works for you, I'd be glad to hear about it. If it doesn't, I wouldn't be glad, but I'd still like to hear about it :) 2016-08-24T17:55:29Z edgar-rft joined #ccl 2016-08-24T18:11:16Z rumbler31: I've had similar problems on windows, and this sounds familiary 2016-08-24T18:37:06Z Xach: pipping: I am using run-program happily for pathnames without spaces. 2016-08-24T18:37:26Z Xach: pipping: but i am getting completely stumped on the C:\Program Files\...\foo.exe issue 2016-08-24T18:37:48Z pipping: Xach: is that with out without cygwin? 2016-08-24T18:40:12Z pipping: Xach: and is the issue ccl-specific? 2016-08-24T18:41:37Z Xach: pipping: I am not using cygwin. I can only use ccl, and I don't understand the error results in ccl. 2016-08-24T18:46:06Z rumbler31: what does run-program call out to on windows, is it just cmd.exe? 2016-08-24T18:46:59Z Xach: I don't think so. But I have had a minor break - using the OLDSCH~1 oldschool DOS names works. 2016-08-24T18:47:04Z rumbler31: if it is, error code 2 just means that the command you passed is unrecognized (usually because it can't be found or is mispelled) 2016-08-24T18:48:42Z Xach: rumbler31: thanks 2016-08-24T18:55:46Z rumbler31: I'll admit i'm trying to find the low level call that I imagine is simply cmd.exe (all your args) and am getting lost. 2016-08-24T18:58:14Z milanj quit (Quit: This computer has gone to sleep) 2016-08-24T19:01:49Z rumbler31: there is ccl::os-command, which passes a string you give it to a call to system(), which loads the user's default shell and passes the string as args to it, which is one way a program can start a new process 2016-08-24T19:02:09Z hjudt quit (Ping timeout: 250 seconds) 2016-08-24T19:02:17Z hjudt joined #ccl 2016-08-24T19:18:55Z hjudt quit (Ping timeout: 244 seconds) 2016-08-24T19:32:30Z hjudt joined #ccl 2016-08-24T19:56:27Z ddp joined #ccl 2016-08-24T20:24:13Z ddp quit (Quit: ddp) 2016-08-24T20:38:21Z hjudt quit (Ping timeout: 250 seconds) 2016-08-24T20:52:44Z hjudt joined #ccl 2016-08-24T21:06:41Z pbgc quit (Quit: Computer has gone to sleep.) 2016-08-24T21:08:18Z hjudt quit (Ping timeout: 244 seconds) 2016-08-24T21:15:34Z hjudt joined #ccl 2016-08-24T21:23:03Z hjudt quit (Ping timeout: 240 seconds) 2016-08-24T21:25:52Z rumbler31 quit (Ping timeout: 250 seconds) 2016-08-24T21:28:34Z hjudt joined #ccl 2016-08-24T21:37:39Z hjudt quit (Ping timeout: 264 seconds) 2016-08-24T21:41:32Z rumbler31 joined #ccl 2016-08-24T21:43:51Z hjudt joined #ccl 2016-08-24T22:02:05Z rumbler31 quit (Remote host closed the connection) 2016-08-24T22:08:39Z rumbler31 joined #ccl 2016-08-24T22:10:52Z rumbler31 quit (Read error: Connection reset by peer) 2016-08-24T22:11:17Z rumbler31 joined #ccl 2016-08-24T22:32:32Z PuffTheMagic quit (Quit: Page closed) 2016-08-24T23:24:51Z rme quit (Quit: rme) 2016-08-24T23:24:51Z rme quit (Quit: rme) 2016-08-24T23:40:05Z rumbler31: ok, that wasn't as hard as I thought to write. a simple c program exercising stat on the filesystem and ccl agree. sometimes st_blksize comes back as a weird value, at least when printed with %d 2016-08-24T23:41:05Z rumbler31: how is the st_blksize supposed to inform implementations? 2016-08-24T23:41:50Z rumbler31: as in, if you ignore it, what could go wrong? 2016-08-24T23:50:46Z milanj joined #ccl 2016-08-24T23:53:53Z milanj quit (Client Quit)