Well, we need to check all the projects and remove outdated ones.

We declare this in the readme:

However, keep in mind that we don't accept mammoth's shit. Only active and interesting projects with good documentation are added. Dead and abandoned projects will be removed.

But, sadly at this moment, this project looks like a mammoth shit itself.

We really need to fix it. I think

Small omission in the guide: it is implied in step 9 that a {} literal should be parsed as a hash-map in the reader, but this is never explicitly stated earlier on. The sentence in question is: "This is basically the functional form of the {} reader literal syntax".

messages, buffer-history-tree and [command, variable]-inspect produce an html view, which is pretty bare bones. We could spice them up, make them pretty, probably reactive (sort columns in messages,…) and with more links.

The more we add introspection information into the help, the better.

skills required: html, css and JS, all through Lisp; lisp to enhance the help.

Could the generated docs be moved to a separate repo? The CI could then commit to that separate repo to keep them updated...

I've added a Rosetta Code page for Janet, but we still need some more examples. I've added an example for the 100 doors problem, but there are many more examples that can be added.

According to docstring M-x sp-clone-sexp RET on (| ()) should yield

(  ())
(  ())

because point is two spaces before an sexp, i.e. not immediately before. But the actual behavior results in

(  ()
   ())

as if it were executed on ( |()).

• smartparens version: 20190103.2309
• Active major-mode: lisp-interaction-mode
• Smartparens strict mode: t
• Emacs

Fri Jul 6 20:15:22 BST 2018

1

Documentation Commands

"C-c C-d f" and "C-c C-d d"

sly-describe-symbol and sly-describe-function are only available with the final key (d, f respectively) used with control.

This (so far), does not match the statements made in [Keybindings](https://joaotavora.github.io/sly/#Keybindings

(defvar *x* nil)
(handler-bind ((error (lambda (exn) (throw 'x :caught!))))
   (setf *x* (catch 'x (car 'x))))

That should swallow the error caused by (car 'x) and assign :caught! to *x*. In JSCL, you can't throw from the handler-bind handler to the catch because the stack unwinds to outside of the catch before the lambda is called.

In Common Lisp, the handler-bind lambd

https://www.site24x7.com/link-checker.html

The internet rots under us, alas. We can but repair.

http://www.psg.com/~dlamkins/sl/cover.html should, probably, be amended to http://successful-lisp.blogspot.com/p/httpsdrive.html

http://www.aiai.ed.ac.uk/~jeff/lisp/cl-pitfalls is now gone; it looks like ~jeff is gone.

The documentation tells you how to create doc comments, but it is not clear what they are good for. Maybe give a hint at how to use them?

(use code documentation)
(print (documentation ...))

It might make sense to have a function help that prints the documentation, like in Python. It would not be terribly useful at the moment, because it seems that the built-in functions and operators

--- ccl/doc/manual/debugging.ccldoc
+++ #<buffer debugging.ccldoc>
@@ -303,7 +303,7 @@
 	    ")
          (item "{param form}" ccldoc::=> "
 	      A form to execute before, after, or around the advised
-	      function. The form can refer to the variable arglist
+	      function. The form can refer to the variable {code arglist}
 	      that is bound to the arguments with which the a