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.

Originally posted by @dimitri in https://github.com/dimitri/pgloader/timeline

That's good thinking, and I think that's relevant for another PR. The PR introducing the statistics singleton should also take care of the following bits of refactoring of the code:

• the singleton is named “state” as I initially though I would update the global state of the migration to be able to know

Currently It's really cumbersome to discover how to tweak the KLISPE APP.
There are a couple of hotkeys and url parameters documented here: http://blog.klipse.tech/clojure/2016/03/27/klipse-manual.html

Here are a couple of ideas - given by @pesterhazy how to do that:

• Like github.com narrow top bar
• Like reddit.com tab-like rider
• Like this

ECB (Emacs Code Browser) is an emacs package that splits the window into tiles. At the bottom is the compilation window. Any time you open certain types of buffers, they always appear there: eshell, shell, JDEE compile and run buffers, SQL, and even the cider REPL. It would be nice if the slime REPL could also behave this way.

Ran into the same issue as #280 with how exactly to use the download.force=t option.

$ ros install clasp
Skip downloading https://github.com/gos-k/externals-clasp/archive/8ad13ba592230f13d11c13b2b0498844ca7083ef.tar.gz
specify download.force=t to download it again.

I tried variations with and without dashes before and after the install subcommand, like `ros install download.force

Hello, I'm getting back to clojure after a while. I am using spacemacs and updated to the current stable cider. However, when I open up a clojure file and do special-lispy-eval, I get this error:

[nREPL] Starting server via /home/mvilpas/bin/lein update-in :dependencies conj \[com.cemerick/pomegranate\ \"0.4.0\"\] -- update-in :dependencies conj \[org.tcrawley/dynapath\ \"0.2.5\"\] -- up

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

I found caveman2.helper functions redirect and url-for really helpful and indispensable for some cases. However, without going through caveman source code, user may not be aware of their existence. It will be great to mention them in doc. Thanks!

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.

Hunchentoot is meant to hide error details from web users unless
*show-lisp-errors-p* is overridden to true. But it doesn't always
hide them.

Here is how hunchentoot renders errors:

a) if there's an error template html file use it, otherwise
b) cook up a message whose level of detail depends on *show-lisp-errors-p*
   and *show-lisp-backtraces-p*

As distributed, hunchentoot contains a 500

--- 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

The default emacs tutorial is confusing, since it refers to keybindings that are modified (for example, M-x being bound to execute-extended-command). One newcomer to Lisp has fallen in that hole today.

I suggest replacing the whole tutorial file with something that in the very least is not confusing to newcomers (e.g. an empty file, or a file linking to #lisp and #clschool on Freenode o

Source location:
https://github.com/McCLIM/McCLIM/blob/4f78e42bbb44b21ea074b818f07f6ed873883759/Documentation/Manual/Texinfo/chap-listener.texi#L157

But the relevant code is commented out in listener:
https://github.com/McCLIM/McCLIM/blob/4f78e42bbb44b21ea074b818f07f6ed873883759/Apps/Listener/util.lisp#L338-L346

One could update that section to tell that it does not work by default. But IM

Implement a function to splice parsed-program objects together in a reasonable way.

Hi,

When doing the example for 1-01-02-more-detail.md on line 246, instead of getting the value of 2.0 (float) i got a value of 2 (integer).Using sbcl 1.3.15.

• (defvar one 1.0)
  ONE

• one
  1.0

• (defun mad-adder (one)
  (declare (special one))
  (let ((one 1))
  (+ one (locally (declare (special one)) one))))
  MAD-ADDER

• (mad-adder one)
  2

• (+ one one)
  2.0

It looks like the upcoming sbcl 2.0.1 release includes changes to move certain symbols out of cl:*features* and into sb-impl:+internal-features+ [[1]]. IIUC, any "non-public" features will continue to work (for now), but issue a warning [[2]].

I haven't tested it, but it looks like we use at least one such soon-to-be-deprecated feature, namely avx2. We should figure out what to do about

• Should tabs be 1, 2, 4, or 8 wide? Or should spaces be used?
• What editor and plugins are recommended?

See gregcman/sucle#43

Vlime has a Vimscript API, but there's no documentation.