Peter Stirling

I'm seeing the following when connection errors occur in clisp on cygwin/windows NO-APPLICABLE-METHOD: When calling #1=# with arguments #2=(#3=#), no method is applicable. [Condition of type METHOD-CALL-TYPE-ERROR] Restarts: 0: [RETRY]...

2 Commits: 1. A simple bug. `lambda-wrap` ends up with a lexical binding for `*ps-gensym-counter*` because the `defvar` appears later in the file. 2. `es-class` and `=>` are the more...

Macro weirdness issue

2

I'm not sure that an issue tracker is the appropriate place to ask this, but I **do** understand it's a convenient place for you. I'm having trouble figuring what is...

`encoder-fn` in [colorise.lisp](https://github.com/kingcons/colorize/blob/f5ed4b342c40257178ebe176108792c01d2e1187/colorize.lisp#L287) assumes the state of `*print-case*`. Wrapping in `with-standard-io-syntax` avoids leaving users confused.