Clojurians Log v2

Btw, clojure.repl/doc is available in joyride as well

I thought that already exists - Joyride: Run Workspace Script that opens up a new selection with all scripts

👋 I hope you will find Joyride intriguing enough to try it out some!

We really want to add that capability. The problem is that VS Code doesn't really allow it. Command palette content needs to be added as part of the extension manifest and is declared in JSON. There's a discussion (well, at least a starter) about it: https://github.com/BetterThanTomorrow/joyride/discussions/14

And, to add some hope, @mauricio.szabo is looking at it a bit. Not sure he has found much traction yet, but we'll see. If we can compromise some with the Ux, it might be doable.

Awesome, thanks for the reply! I left an upvote to the discussion. Really hoping to see this come to be in the future!

Hmm, perhaps Joyride’s way of running commands could also wrap around vscode’s own commands? So rather than using the default Cmd/Ctrl + shift + P, joyride could provide its own thing that lets you run all your joyride scripts + all of vscode’s commands? Just as a sort of workaround for vscode not providing the feature itself

The neovim extension does something like that

Would putting the joyride-provided commands in a submenu (like where you select repl type after running jack in) get around the manifest issue? Suboptimal UX for sure, but something is better than nothing

Not possible at the moment. I filed an issue about it. https://github.com/BetterThanTomorrow/joyride/issues/36 Thanks!

Ah, thanks

Does it work if you first load some namespace in your user scripts directory? I think it should.

It seems to only work if I run the user script that I'm requiring (which of course means the ns is already loaded). I ran userA.cljs from my user scripts dir, and then ran wsA.cljs from my ws dir, which requires userB. This results in the wsA run reporting that it can't find userB.cljs (in my workspace scripts dir).

Thanks. We probably need to look for sources in both locations, right @borkdude?

Would you like me to open an issue with the repro and so on so you can take a look at your convenience? I only asked here because I saw that :load-fn in the sci context appeared to only search the workspace directory, and I thought the user dir might have been considered and rejected already.

Issue welcome.

will do - tangentially, thank you for Joyride - really cool idea, and I'm sort of hoping to introduce it to some VSC users at work to expose them to some clojure in a context where many languages can't go

Awesome! That’s one of the goals with Joyride. To bring Clojure to the doorstep of developers who might find what Joyride offers to be intriguing enough to warrant using a new language.

Yes, it should search the user dir as well :)

Should it behave like this: A require in a user script, searches within the user dir and a require in a workspace script searches within the workspace dir? Or should it always search in both?

Good to hear you are enjoying joyride @highpressurecarsalesm :)

What I'm wondering about: what if your workspace scripts rely on user scripts? I guess your teammate also wants to use those workspace scripts but then they are incomplete right?

But maybe we should just let people decide how they want to deal with that and just allow it

It definitely opens up the ambiguity - in my mind, at the very least, a workspace script might want to re-use code made available by a user script - the other way around doesn't make as much sense to me, unless people wanted to make that a sort of hacky (IMO) polymorphism mechanism.

oh, I misread what you said - yeah, I guess it sort of goes both ways - I might have a bunch of workspaces where I want to re-use functions, but other people might want to use the same workspace scripts

What happened with v0.0.6? Well, let's say we really need to move the release process to CI...