Because I need to do it with the new boots:
If your snowboard boot liners are heat moldable and you want to do it at home, we’ll show you how: You’ll use rice, a microwave, a short two-by-four, and several pairs of socks.
Ran into a weird situation where clojure-lsp in Emacs behaved strangely only when working on one particular repo. While function reference counts were shown, no tests were. In fact, tests were getting included in the reference count. A colleague loaded the same project and everything was working normally so it was definitely some configuration on my end.
I could see clojure-lsp reported all other repos used their root correctly (all created and used the repo's
.lsp/.cache) except for this particular one, which was instead creating and using a cache one parent up and I could not understand why.
Of course, it all ended up being looser-error as I discovered I must have inadvertently told lsp to not include the repo's root in its watch list. I didn't know where clojure-lsp tracked its session list but got it by getting the value of
lsp-session-file, which pointed to
~/.emacs.d/.lsp-session-v1. In there I found the repo's path was included in the second list which contains ignored paths. Removing it from the list forced lsp to prompt me again after a
lsp-restart-workspace and everything behaved as expected from then on.
A neighbor who works by us had been having this weird issue where the number-pad on his iMac stopped working causing weeks of frustration trying to get work done. He asked if I knew anything about Macs so I offered to help out and eventually discovered it was due to an accessibility setting called "Mouse Keys" that configures the number-pad keys to control the pointer. I didn't know about this and, of course, they had no idea what had caused it to become enabled so it seems weird that this setting would turn on by itself, but alas, here we were.