Daniel Kochmanski

it is console REPL prompt who eats the first line (via read-line probably). It is easily avoided if you do `(loop (sleep 1))` (of course more sophisticated logic may be...

> ps: and my 2 cents: IMO cl-annot's export annotation is very handy and less error-prone than the default to export symbols, because they are next to each other. It's...

There are more problems with the input rescanning loop. I'm rewriting the input editing stream implementation, so I'll keep an eye to get this right too. Thanks for the report.

this looks interesting, thanks! as of guidance, I don't have any strong opinion. you may search the irc channel logs whether there is something relevant (i.e https://irclog.tymoon.eu/libera/%23clim?from=2022-02-23T06%3A28%3A12&to=2022-08-30T18%3A28%3A12&search=input%20method&by) I'm currently rewriting...

(and it extracts default-skeleton implementation from the quickproject.lisp into default-template.lisp)

the last commits add possibility to rewrite file names (with the very same rules used in the files)

in dev-commands.lisp: ``` ;;; The background evaluation feature is neat, but there are thread ;;; safety issues doing output to streams, special variables have ;;; unexpected values, and input doesn't...

This issue should be solved by providing unique streams for the Listener evaluated requests which get piped back and forth to the Listener frame, so there are no races and...

no, I can see problems, when I try to `read` with background mode. There is a race for key presses between CLIM event loop and function `cl:read`.

Probably way to tackle it would be binding a separate stream for expression input and making McCLIM forward it there. Same goes for other default streams.