freenode/#lisp - IRC Chatlog
Search
22:46:18
manish
gFtnR4hHjfBpYxDcq5GMVaq3nsdaupo1vdrxoZXcgfmr8DAFiwIrkuFRvs9vM3uzuBOc7vZwZvCT0xjdyMVOvnW6jk4mGM5Wff9pT58eXthiiH5CStWcI2GB
22:46:25
manish
e3iSIVifBCJZY6tolz3loRPe2RB1I85Twtdl4NhD618nlCUzDDeRYQC8ieVx68RrMUvcBAXLGuHGeHmzrFT9KbrmcHXuLTfrRYlfGIZ7WEbDeW6j87FgmPj1
22:46:29
manish
hU4OdFANEZhUK2nlXn8I9lnfWXxtiFiudeNW1IUFPbHxuQMQYWDf1YAqa3FV6UT06dB7gbCgqHSaZKcHM7AW8n8vEBDK5Qjif9N4XWyATqogK0RbkL5DtpJ0
23:16:13
aeth
The internet is probably like 99.999% spam. That you can mostly avoid spam is a miracle, but sometimes spam slips through the cracks of a system.
23:18:25
z3t0
This is probably a very basic question... How do I copy file1.txt to file2.txt in commonlisp? I have been using uiop:copy-file but that fails because the target file doesnt exist. I thought about reading the file then writing it as strings but then I also have non string files
23:22:22
z3t0
ah it worked! I was missing a "/" in the target path and didnt realise it was writing the file, just in the upper folder
2:12:45
Josh_2
I lead you all on, sorry, I am stuck but I'm totally burned out so I think Im going to go to sleep instead
9:26:53
beach
nullx002: What is the reason for your question? I am asking because you seem to be new here. I don't recognize your nick.
9:28:29
nullx002
yes, using bit of lisp and emacslisp for few years, but nothing special. was off the grid for 3 years..
10:16:39
pyc
how can I get the "CL-USER>" prompt that I see in most documentations. If I run CLISP I get only "[1]>" prompt and SBCL gives me "*" prompt. Where does "CL-USER>" come from?
10:18:53
beach
pyc: Unless you use something like SLIME, programming in Common Lisp is going to be very painful, and you will be disgusted and abandon it.
10:19:43
pyc
beach: why is that? I have been writing standalone .lisp files and executing them as "clisp foo.lisp". Seems to work just fine. Not much different from Python or C.
10:20:35
pyc
beach: can you explain why you would be disgusted? Maybe as a beginner I don't realize why my way of doing Lisp is suboptimal.
10:21:01
beach
I guess if you are used to inferior programming languages, you don't know what you are missing.
10:21:07
pyc
drbluefall: Which one is more popular between SLIME and SLY? And for what reasons would one recommend SLY over SLIME or vice versa?
10:22:17
beach
pyc: In Common Lisp, you develop code interactively, one definition at a time. You often compile top-level forms immediately after you type them.
10:23:04
beach
pyc: You often switch between the code and the REPL to test a single function after you typed it.
10:23:20
pyc
beach: thanks! I will stick to SLIME then. I tried SLIME once briefly but did not know enough to be able to realize its usefulness.
10:24:56
Nilby
pyc: In CLisp you can set the prompt with the custom:*prompt-.. variables, e.g. (setf custom:*prompt-start* "foo")
10:26:27
pyc
beach: yes, thanks. that is convincing enough. i will stick with SLIME and learn it more.
10:29:00
beach
Well, I guess it sort of is, if you count realizing a wet dream by an incompetent hacker without training.
10:29:47
beach
Oh, and convincing incompetent management about what programmers to hire, and what language to use for the next project.
10:30:18
carkh
i remember reading a blog post about some company that couldn't get out of cobol because of its outstanding decimal numbers processing
10:31:26
drbluefall
Like, say when it comes to web, I will be the first to admit that I will sooner reach for Rust
10:33:04
carkh
yes, i think i'll stick to clojure for the web, rust is annoyingly low level for that kind of stuff
10:35:07
carkh
that borrow checker gymnastic seemed annoying to me. Though i can see how this is all usefull for low level work
10:38:01
drbluefall
For me, the draw was more the ecosystem than the language itself (although the language felt much nicer than what I was using before).
10:39:05
carkh
that's one thing missing here, a competent packge system (even if quicklisp is a big step in the right direction)
10:40:35
drbluefall
quicklisp I find usually sufficient, although something akin to cargo would be absolutely *amazing*
10:41:57
drbluefall
I think the most painful experience with packages and dependencies was in C/C++.
10:42:59
moon-child
the main essential complexity with c is that they tried to make dynamic linking work. Dynamic linking is a really nice idea, but it's proven itself to be unworkable