Fork me on GitHub

I cloned the re-frame.git repository and cd'd into the examples/todomvc directory. Its README tells me to use '''lein-watch''' to kick off a clean build. How does that translate to Jack-in with Calva, i.e. is that enough information to select the project type? It seems to me I should choose '''Leiningen + shadow-cljs''' or '''Leiningen + lein-shadow''', but I don't know really on which grounds I should pick one or the other.


I’ll have to check the example before giving and answer, @roger429. I’ll try to do it in a moment. Remind me if I seem to forget.


@pez Thanks! of course I should try them out myself, but that's more like trial-and-err than making a well-reasoned choice.


I've got the app running now, so now I should try to reproduce the choices I made and attach a mental map to that


I should write some more about this question in general to the Calva docs.


I chose 'Leiningen + lein-shadow' as project-type; ':client' for build to start, and 'watch' as the alias to launch


@pez: I would welcome that; Step 3 on the page is for newbies quite cryptic: we don't know yet about project types and profiles, and how to determine what some project on github uses.


Thing is that this (from a bit further down the page) will be true for some time to come: > You will need some basic knowledge about the project and the project type terminologies to answer the prompts. But it should probably be mentioned earlier and there should probably be some pointers about how to figure these things out and encouraging experimentation and such…


There are ways Calva could be smarter, but I have avoided that so far because I am not smart enough to forsee all the kinds of setups ingenious Clojure devs invent… 😃


I agree it's probably some rabbit hole. Maybe we can use a Wiki page to collect some hints, like 'If you see [...] in a file prj.lein, choose profile type [...]' etc. When in due time enough hints are collected, some wisdom may be extracted from that which is worthy to be included on that page.


I think we between us (in this channel) we already have info that should go on the docs page. And probably also Calva can help you find that page when jacking in.


And crowdsourcing more via the wiki is an awesome idea. We should do that as well.


It is publicly editable for a reason.


> And probably also Calva can help you find that page when jacking in. That would be neat, e.g. to show an entry 'Need a clue? Visit' in the drop-down menu. Or change the place-holder text to something like: 'Please select a project type (see [link to wiki-page] for clues)'


I like it!


Thanks for this! I edited the title slightly for more clarification and linked it in the docs here at step 3:


This may be an old question but can I use the Calva - Paredit outside of Clojure? - It seems that I remember it changed from being a separate thing to part of Calva generally. I want to use it with Racket and Fennel that I am starting to use VSCode for


That is some awesome tips @roger429. Thanks!


@tbrooke There were a time when Calva Paredit was a standalone extension. But it is since then an integrated part of Calva itself. I have tried disentangle it enough to be able to build a standalone extension from it again, but not been able to finish that. However, there was a dev who I spoke to recently, don’t have access to my conversation history though,… anyway, he had also started this in a separate repo. And he said he might have time during christmas to tend more to it. It was not specifically Paredit, but the things in Calva that it relies on. So, we might get there again, but not in a jiffy.


All that said, Calva Paredit is quite Clojure specific. I guess it should work on scheme and other code as well, but I am not sure about it. Not familiar enough with those LISPs.


You could try this paredit extension: Which is quite limited compared to Calva’s but Calva users made do with it for quite a while.


Thanks I’ll check them out — I could use Emacs but now that I’m in VS-Code it would be nice to have everything in one editor


There is also this one, which is a fork of old Calva Paredit, which is also quite limited, but probably better than no paredit 😃


Has anyone tried this vsix on Windows?


I've been using my own dev branches lately. Will try to figure out a workflow where I can use the lsp changes at the same time.


Since I asked this, I installed Windows 10 in a VM on my linux machine and tested lsp. I didn't notice any Windows issues


There are 1 or 2 issues in the lsp repo about Windows though. I need to check those