Package-local nicknames in Common Lisp
Warning: this is a rant.
Warning: you have been warned.
Note: actually worthwhile content starts in the second subsection. You are free to skip the first one.
|; Short guide to TCP/IP Client/Server programming in Common Lisp using usockets|
|; The main reason for this guide is because there are very few examples that|
|; explain how to get started with socket programming with Common Lisp that I|
|; could understand. After spending a day trying, I finally came up with a small|
|; bit of code that makes it easy to understand the basics. I've written this|
|; primarily for myself, but should help others get started as well.|
|; As usual, we will use quicklisp to load usocket.|
Quickdocs.org now provides project badges for Quicklisp projects. It shows Quicklisp dist version when the project was updated last.
Once the project owner adds this badge to their README file, it will inform the project is ready for Quicklisp and its documentation is available on Quickdocs.org.
It's available, however it was just added in this morning at whim and it may still have issues. Please try it and tell @nitro_idiot if you encountered any issues.
|(defun multiline? (string)|
|(position ?\n string))|
|(defun multiline-comment (string)|
|(concat "#||\n" string "\n||#\n"))|
|;; Note: Redefining to send the error message too.|
|(defun chebert-eval-async (sexp &optional cont package)|
|"Evaluate EXPR on the superior Lisp and call CONT with the result."|
|(declare (indent 1))|
|_describe -t commands "fabric targets" target_list|
|'status: Status messages, i.e. noting when Fabric is done running, if the user used a keyboard interrupt, or when servers are disconnected from. These messages are almost always relevant and rarely verbose.'|
|'aborts: Abort messages. Like status messages, these should really only be turned off when using Fabric as a library, and possibly not even then. Note that even if this output group is turned off, aborts will still occur – there just won’t be any output about why Fabric aborted!'|
|'warnings: Warning messages. These are often turned off when one expects a given operation to fail, such as when using grep to test existence of text in a file. If paired with setting env.warn_only to True, this can result in fully silent warnings when remote programs fail. As with aborts, this setting does not control actual warning behavior, only whether warning messages are printed or hidden.'|