freenode/lisp - IRC Chatlog
Search
3:48:49
loke
I seem to recall there is an emacs package that does something similar to top, in a buffer?
3:50:01
malice
emaczen: if you just want to check how many cores you have though, nproc is more than enough
3:51:14
loke
That saiid, I figured that emaczen also wanted to monitor CPU load during his threading examples.
3:53:08
malice
also, if you have some simple task that you just want to parallelize, GNU parallel is also a good choice
5:35:13
aeth
shka_: alexandria is always going to be the top downloaded library because of holes in the standard.
5:36:50
aeth
Not everyone works with text, almost everyone works with something that alexandria covers because it's more general.
11:36:05
schweers
I have a question regarding the debugger. Suppose I have code of the structure like here http://paste.lisp.org/display/354072 Further suppose I’m already single-stepping in the debugger. Can I step over the complete loop to (some-other-code)? I’m using SLIME and SBCL.
13:14:04
pjb
schweers: have a look at cl-stepper, so you may use ccl (or any other implementation) in development.
13:15:47
dlowe
I would expect, not having used it, that it simply uses the condition raised by the (break) form.
13:21:40
dlowe
but compilation in the normal lisp environment is so trivial that I'm not sure anyone considers it an inconvenience
13:23:52
dlowe
schweers: in sbcl, if you (TRACE FOO :break T) it will break on every invocation of FOO
13:25:48
dlowe
I mean, if you're *at* the position you want a link for, there's no convenient button
13:37:20
schweers
this is the chapter in question? http://www.gigamonkeys.com/book/practical-a-simple-database.html
13:37:32
dlowe
the standard academic model is to say what you're going to say, then say it, then say what you just said
13:38:07
butterthebuddha
Okay cool, ty. It's a little overwhelming because lisp is very different from everything else and he goes a little quickly
13:38:56
Shinmera
The first chapter is a bit hectic, but he tries to show off something "cool" to get you interested and slows down afterwards.
13:39:17
Shinmera
Which in my opinion is fine. It could've maybe used a disclaimer of some sort though.
14:21:27
oleo
i had some lib there which contained lisp-unit, and antik want's the real lisp-unit package...and even tho i removed the ~/common-lisp/systems/bla.asd links it finds them in the ~/common-lisp/system directory still....
14:24:06
oleo
and i have no (:tree....) in my systems-registry.conf in .config/common-lisp/source-registry.conf.d/ that points to ~/common-lisp again
14:37:47
oleo
i could only solve it thru moving those libs in the source there to another out-of-tree location....
14:38:44
oleo
only the systems dir of symliks to the real asdf files such that you know which you want to activate....
14:41:09
schweers
it’s searched recursively? I was annoyed that it’s not, but it seems that I misunderstood
15:20:59
oleo
everything (.asd files) which you link from the commonlisp/source to the common-lisp/systems directory is meant to activate that
15:21:02
jackdaniel
oleo: if you have directory structure foo/foo.asd foo/tests/foo-tests.asd and you don't search recursively, you don't have tests
15:21:56
oleo
you can cd to common-lisp/systems and do a find ../source -name "*.asd" -exec ln -s {} \;
15:22:39
jackdaniel
well, I can do a lot of things, but searching recursively is the most intuitive to me as well
15:23:39
Shinmera
Seems pretty reasonable to me that it would search recursively in a directory called "systems".
15:23:46
jackdaniel
asdf had problems with backward compatibility numerous times. one side of the coin is that it breaks stuff, the other one it isn't tied to design which maintainers consider broken
15:25:12
jackdaniel
oleo: if you link each asd system individually in common-lisp (without putting directories), it won't go recursively
15:26:56
oleo
anyway, you could divert asdf to detect if it is on such a system without symlinks....
15:27:53
Shinmera
anyway, if the default behaviour of ~/common-lisp bothers you so much you can just make your own and define its behaviour explicitly in ASDF's source registry language or whatever.
15:32:30
Fare
I used to try not to follow them in older versions, because that was the most predictable and also the way to avoid endless recursion.
15:33:09
Fare
rpg recently added a layer to avoid endless recursion, and enabled following them on implementations such as SBCL where we were previously not following them.
15:34:35
Fare
~/common-lisp/ WILL be recursively searched, but you can use to source-registry-cache to stop the search