Clojurians Log v2

Is it OK to post your own little projects with babashka here? Assuming yes, it's dinky but it's been so incredibly helpful. I get a ton of passworded PDFs from e.g. my CPA. It's all security theater (ask me how I know) and the passwrods are consistent. I have better ways to keep that data safe so I want to take the passwords off. This does that with a set of passwords, configurable, stored in 1Password: https://github.com/lvh/pdfunpassword it's a perfect example of "slightly too complicated for me to like writing it in bash, still super useful". it's not clj-kondo but it sparked joy 🙂

So what's the latest thinking on cider and babashka nrepl? It is a real problem that babashka identifies as clj and gets sent my Clojure code when I have two (clj, babashka) REPLs open, but on a mixed project. The application is supporting babashka in clay, which uses cider for it's emacs integration. The user would have two REPLs in this scenario, one for working on the babashka notebook (and clay sending forms to it when rendering it) and one for clay itself. Long term we might also just have a babashka port of Clay, but for other dialects the issue might come up as well.

Would it be a good addition to babashka.fs to wrap Path#getRoot ? I find it useful when I'm rebuilding an absolute path from components & want the same behavior on Unix & Windows. On Unix, it's easy to assume the root of an abspath is "/" (for a local path, at least). On Windows, it's often "C:\", but not always. One could parse the path string, but Path#getRoot is cleaner & better documents the intent. One important caveat: It's not helpful for dealing with non-native paths, say a Windows path on Linux.