LispForum

It's easy to print things differently depending on the context, but then you have to keep track of context. How does a selector know if it's in a list or not? It probably doesn't, so you'd need to leverage the pretty-printing mechanism (as pjstirling suggested). Erik Naggum once posted a throwaway e...

Seems like it might be easiest—if not the right thing in your case—to just look for any keywords to delimit the associated expressions, rather than specific keywords. Sticking them in a property list makes the rule definition a bit more tractable: (defun rule-definition-plist (body) (loop with p...

The Web site Dark Chestnut has some articles involving Clack, like this one.

The mailing list had a question about it: [Openmcl-devel] *trust-paths-from-environment* under Windows? I guess CCL has its reasons for not using the HOME variable on Windows—security reasons, maybe?—so some modification would be involved in making that happen.

You could specify the same operations from the command line:

The welcome-message thing with portable-threads is mentioned here—that author's version of portable-threads has killed the message. Aside from changing the library code, you could just muzzle standard output like this:

It's a quoted list—you're passing in the literal expression (gethash "PASSWORD" hash) instead of its value.

I don't think I'd use append for this—it seems to call for something like this for the right-tree case:
And something similar for the left-tree case.

An iterative approach isn't any less "Lispy" than recursion. The recursive version is tail-recursive, so replacing it with a non-recursive version is perfectly reasonable.