1:01:09raltloke: I've seen in some logs that you managed to get signals from dbus, would you care to share some snippets to do this? I want to subscribe to a known signal but unclear what I'm supposed to do.
2:59:39aethThe only issue is that it won't error if it's not even
3:00:27Alfr_martinjungblut, careful if list has a odd number of elements, then on the last iteration b will be nil; just keep that in mind that it won't error.
3:00:35martinjungblutactually, I kind of need it that way
3:00:35aethdestructuring bind will force an error, unlike LOOP's destructuring, but it's not as elegant. (loop for sublist on '(1 2 3) by #'cddr collect (destructuring-bind (a b &rest rest) sublist (declare (ignore rest)) (cons a b)))
3:01:01martinjungblutwell, not need, but the nil is fine
3:01:27martinjungblutas a newcomer, I have to say, Common LISP is a hell of an environment to write software in
3:04:03aethOh, and there's an in between route, which is to do the sublist thing, but then destructure it in the next LOOP variable instead of having local d-b variables.
4:01:49Bike"time zone n. a rational multiple of 1/3600 between -24 (inclusive) and 24 (inclusive) that represents a time zone as a number of hours offset from Greenwich Mean Time. Time zone values increase with motion to the west, so Massachusetts, U.S.A. is in time zone 5, California, U.S.A. is time zone 8, and Moscow, Russia is time zone -3."
4:48:43beachI am doing very well thank you. I am currently working on updating the SICL specification to adapt it to the many new ideas and extracted libraries that have happened since last time I worked much on it.
8:12:43beachnpfaro: The mismatch function is a lot more versatile.
8:13:20beachnpfaro: Perhaps it is unorthodox because most languages don't allow keyword arguments to modify the behavior, and they don't allow "out of band" return values.
8:14:10beachnpfaro: Lots of things about Common Lisp are that way, luckily. CLOS, the condition system, macros, keyword arguments, multiple values, etc.
8:18:02npfaroThe only issue is that mismatch returns nil when the arguments are equal, so (zerop (mismatch ...)) breaks when they're equal
8:18:09beachIt's a bit sad, though, that the intrinsic limitations of other languages would make them "orthodox".
8:21:26loke[m]Can't you do something like (NOT (MISMATCH s1 s2 :end1 #1=(min (length s2) (length s2)) #1#))
8:22:33NilbyIn my own far off world that matters little, I say begins-with and ends-with, because I find the mismatch and search forms unintuitive.
8:23:17loke[m]I agree with that. I prefer using the Alexandria functions for that.
8:24:20beachloke[m]: Did you mean NULL rather than NOT?
8:25:03loke[m]beach actually I meant NOT, because the CLHS specifically says that MISMATCH returns “false”