libera/#commonlisp - IRC Chatlog

20:08:19 jmercouris Why does uiop accept arbitrary keywords and not complain?

20:08:31 jmercouris I have to say, I was expecting at least some error

20:09:00 jmercouris for example: (uiop:launch-program (list "ls") :oputput :interactive)

20:09:08 jmercouris "oputput" is not a keyword arg for launch-program

20:09:30 jmercouris anyways, that's the end of my rant

20:09:40 jmercouris a heads up for anyone who hasn't yet encountered this

20:34:41 bike jmercouris: launch-program specifically has &allow-other-keys, probably because different implementations might have their own keywords

20:47:16 jmercouris bike: aha, that makes sense

21:42:41 _death maybe it would've been preferable for it not to have &allow-other-keys, so that someone who wants to pass implementation-specific keys would have to specify :allow-other-keys t

21:49:10 _death it also passes :allow-other-keys t to the implementation's run-program, which is why it doesn't signal an error

23:41:01 jmercouris alright so I have a most perplexing problem

23:41:03 jmercouris http://dpaste.com/HRALHZQ5V

23:41:26 jmercouris I am writing "\\\\n" to a socket and on the receving end I am only reading "\\n"

23:41:30 jmercouris why is this?

23:41:56 jmercouris who is swallowing the escape characters?

23:43:52 jmercouris is it lisp that is swallowing them?

23:44:00 jmercouris presumably, because it thinks I am trying to escape something

23:44:28 bike the lisp reader, yes

23:45:10 jmercouris bike: I did a stupid hack to be able to write strings, so the reason you see "\\\\n" is because I had just "\\n" before, and something was getting lost on the way

23:45:16 jmercouris so I added more backslashes.

23:45:23 bike if you do (write-string "\\\\n") you should see \\n

23:45:41 jmercouris wow that blows my mind

23:45:43 bike not sure from your paste whether lisp is the sender or receiver, though

23:45:48 jmercouris lisp is the sender

23:45:52 bike ah ok then.

23:45:53 jmercouris javascript is the receiever

23:45:58 jmercouris can you think of a better way for me to do this?

23:46:06 jmercouris because right now I am doing a stupid str replace to add more slashes

23:46:16 jmercouris it is code being outputted by parenscript

23:46:17 bike as long as we're on this topic, \n doesn't do anything special in lisp. it'll just be a backslash and then an n, so if you want a newline you're out of luck

23:46:37 jmercouris I know, it is because it is being used by JS

23:46:42 jmercouris let me post a little snippety snippet

23:46:55 jmercouris http://dpaste.com/FN3UDZH3V

23:46:58 jmercouris so you see the problem of course

23:47:07 jmercouris I have this string, that I am then writing, which of course will become malforemd on the other end

23:47:24 jmercouris (write-string "'hello\\nworld';") -> 'hello\nworld';

23:47:26 jmercouris which is now, wrong

23:47:41 bike is it?

23:47:50 jmercouris yes it is

23:48:05 jmercouris the correct string would be "hello\\nworld" as seen in the world of JS

23:48:17 jmercouris but I am just sending "hello\nworld" and JS is thus losing its mind

23:48:45 jmercouris so how can I have a string "hello\\nworld" and send it to the socket AS IS without my precious backslash being stripped away

23:48:59 jmercouris or alternatively, how can I modify PS to print more backslashes...

23:49:04 jmercouris since I know some will be consumed

23:49:16 bike so you want to send hello, then two backslashes, then one n?

23:49:23 jmercouris that's correct

23:49:33 jmercouris I'd like to literally send "hello\\nworld"

23:50:06 bike ok. well to get that from the lisp reader you'd write that as "hello\\\\nworld". but i don't know what parenscript is doing.

23:50:16 jmercouris I'm already doing that

23:50:21 jmercouris because I figured that is what was needed

23:50:26 jmercouris but it is just so wrong feeling

23:50:40 jmercouris I am doing a stupid string replace

23:50:59 jmercouris like this: (str:replace-all "\\n" "\\\\n" message)

23:51:11 jmercouris but I will see if I can mess with parenscript to output more slashes

23:51:44 jmercouris thanks for your help bike

23:57:52 bike sure thing.

7:50:10 splittist jmercouris: you might feel it is overkill, but cl-interpolate can be useful for dealing with 'c-like' strings https://edicl.github.io/cl-interpol/

7:50:34 splittist (interpol, not interpolate, obnov)