15:16:47schweersI can’t really comment on paredit, as haven’t used it for a while, but lispy does this, and I’m pretty sure the two are somewhat identical feature-wise
15:16:50rpgjust using the cheat sheet, I don't see a paredit command to comment out an sexp.
15:17:45schweersi.e. when point is at "|" in this expr: (let ((var1 ...)|(var2 ...))...) using paredit-comment or whatever should do The Right Thing
15:17:59schweersi.e. insert a line break after (var2 ...)
15:19:09schweersdoes this help you? https://stackoverflow.com/questions/4288339/how-do-you-comment-out-all-or-part-of-a-lisp-s-exp-using-paredit
15:47:29rpgI like paredit, but there are definitely cases where it feels too rigid (like where I want to copy a set of let bindings, but not the body that comes with it. I would like it more if it were easier to say "yes, I know that the parens are messed up, and now I'm fixing them."
19:13:14clintmHow would I get the actual error from a error with asdf running a grovel operation? A header is probably missing, but there's no helpful message at the top of the slime buffer to guide me.
19:13:36clintmI went through the backtrace as well, to no avail.
19:17:08phoe...so if my question about testing frameworks was not answered, I think it's time to write some Lisp.
19:29:14clintmoooooh, the errors went to the terminal the image is running on and not over swank. Good to know.
19:31:14phoethis sounds like a bug. if they're Lisp errors, then these errors should definitely go to the swank output.
19:32:41phoe...oh. At this point, they won't go to swank since they go to the Unix stdio.
19:32:50clintmyea, they are. Missing headers... which are in /usr/local/lib, but are special *invisible* headers :P
19:33:14phoeclintm: my suggestion is basically running the SBCL image in some sort of tmux, so you can ssh into the server, tmux attach, and read what's going on.
19:33:54clintmAs a matter of fact, that's exactly what I do :) I just hadn't looked at that term window in a while.