kchan!

I guess this would be a nightmare to do for webpages on the large that ab(use) arbitrary JavaScript. But it could be very useful for Nyxt applications in user-internal-buffer so...

> And, in my view, that's the main difficulty: discovering which symbols are lexically established at the current point. Suppose you can discover a superset of symbols which could mean...

This might have some performance issue however. I can imagine to account for exported symbol one only need to refresh when a package is (re)defined, but to account for lexical...

I haven't got chance to hack into SLY internals so don't take what I'm going to say seriously, especially the highly opinionated "best"/"better" etc... Recognizing some special form will do...

Do you have any idea what are those ALEIN-VALUE thingies? I'm also encountering them when optimizing a floating-point program.

Any update on this? Is the compatibility concern that prevents this to be added to `Sauron`? This function is introduced in probably `emacs 26` (we can always make a switch...

Some more issues: 3. Turns out `polyline` breaks completely when I use `(with-pen (make-pen :stroke +black+ :weight 2) ...)`, even without any transform. 4. The thickness calculation when using `line`...

Ah, that's a feasible solution, and I'm already doing it :) [https://github.com/BlueFlo0d/insecure-lock](https://github.com/BlueFlo0d/insecure-lock) I think a new customization option is not strictly necessary because users can do this themselves relatively easily....

Sorry Electron sucks but uNiX sucks more [Unix and C are the ultimate computer viruses.](https://www.dreamsongs.com/RiseOfWorseIsBetter.html) Please replace Electron and UNIX spinoff and copycats support with Lisp Machine supports and CLOSOS...

It's a wild hack and as for now I'm not sure if it's useful either. I'm using `:invert`. This may enable tight integration with case-sensitive systems, in my case Unix....