trying to migrate to calva from emacs, so far so good. It's painful reprogramming the central nervous system so brutally.

I noticed the hover-help to get the docstrings doesn't seem to be working. I'm wondering if I have everything setup right.

also noticed "go to definintion" doesn't work - so same question

And same answer 😀. It is probably due to insufficient nrepl dependencies. Calva doesn't yet inject them for you. If you scroll up some, you'll find a long and beautiful command line that injects everything that's needed (and then some, if you're not using figwheel).

Oh, noes, that had suffered the Death o’ Slack! No worries, though, here goes:

lein update-in :dependencies conj "[nrepl \"0.6.0\"]" -- update-in :dependencies conj "[cider/piggieback \"0.4.0\"]" -- update-in :plugins conj "[cider/cider-nrepl \"0.21.2-SNAPSHOT\"]" -- update-in "[:repl-options :nrepl-middleware]" conj "[\"cider.nrepl/cider-middleware\"]" -- update-in "[:repl-options :nrepl-middleware]" conj "[\"cider.piggieback/wrap-cljs-repl\"]" -- repl

^ @hoppy ^

will give that a try. I assume the piggieback is cljs only?

A lot of that stuff is cljs only. But afaik they don't get in the way for clj coding.

yeah, that lit things up - thanks

It might make sense to plop that magic lein command into the wiki - it will trip up even a patient n00b

salvaged/groomed from one of the github tickets & your comments above.

I actually added it to the wiki first page after I had pasted it here for you. 😃

😎

But, yeah, it should go into the Getting Started page as well. Feel free to edit the wiki.

Hopefully it should be history soon, when we get the jack-in released.

a connundrum likely inherited from cider. Getting that guy setup was a pita too, although it has gotten a lot easier recently

If you are of the brave type, @hoppy, I welcome you to help beta test the new REPL window. It makes things quite a bit more like with Emacs.

I had always looked for the "hey stupid, this is how the pieces fit together, and what does what"

birthing a cljs repl was vexxing

The cljs repl story is quite nice with Calva I should say. Once you have gotten it connected, at least.

With Cider I get a bit confused which repl is working for me, but with Calva it is easy to know that and also easy to switch.

I will play with that shortly, and I'm happy to help/hack on wherever I can be of use.

Here’s the dev build with the new REPL window, anyway. It has quite a few rough edges, but I still find it more productive than the released Calva.

I'm trying to wean myself off emacs, this seems a much saner path. I need to be able to get new people into clojure, and as long as we have "step 1, master emacs" we are toast

Unfortunately I'm such a cider-freak it has bound itself to my spinal column, and I can't get much done without it.

Haha, yeah, that is sort of the why Calva exists. Some say it’s good to weed out the not-so-brave, but I kinda feel it is better to have this option.

There’s still a long way to go for Calva to give Cider a match, but VS Code is nice, and we’re slowly improving things.

I think this is the right trajectory. Guy that works with me touts cursive. I plopped that on my laptop and fired it up, and the damn thing did a short-field takeoff when the fans spun up.

way too heavy

And, Calva owes most of its functionality to The Orchard anyway. 😃

yeah, and I think that is where history will erect the statue of BB

Calva really is distilled from Cider.

Nice idea with a statue!

not sure how to consume the .vsix (I'm a vscode noob). I tried to just do "code <blah>" like I found instructions for, but it just tries to open it like a data file

nm, got it, needed --install-extension

wow. new world

Oh, I’m sorry, was afk. What I do is I do it from the extensions pane in vscode. There’s … menu there at the top right.

no worries, all good. Trying to find my way around the new wonderland

The command palette is your friend in vscode. cmd+shift+p on mac.

Type in that menu and it will filter the commands. Calva is a good filter. 😃

yeah, been all over that

Also, I have changed some paredit key bindings on my machine to match those in Cider.

Im sure config hacking will become a new hobby

Well, much less so than with Emacs, hopefully. 😃

That said, I have this in my settings.json:

"editor.tokenColorCustomizations": {
        "textMateRules": [
            {
                "scope": [
                    "meta.comment-expression.clojure"
                ],
                "settings": {
                    "fontStyle": "italic"
                }
            },
            {
                "scope": [
                    "constant.keyword.clojure"
                ],
                "settings": {
                    "foreground": "#9cdcfeff"
                }
            },
            {
                "scope": [
                    "punctuation.section.expression.begin.clojure",
                    "punctuation.section.expression.end.trailing.clojure"
                ],
                "settings": {
                    "foreground": "#999"
                }
            }
        ],
        "[Default Dark+]": {
            "textMateRules": []
        }
    },

I'm having some confidence trouble with eval-file

Never mind the comment-expression things, they are for a dev build of Calva where I try to tokenize comments.

What about eval-file?

somethings just off. I got it bound to a key, and I wee the evaluation message happen, but it doesn't seem that the symbols get defined

it's weird

It’s a bit worse in the dev build you are using. It eats up more of the error messages… But it’s probably due to some form not compiling. Try evaluating them one at a time from the top. (`ctrl+alt+v space` is your friend here).

that's likely what's going on, this is code I'm actively hacking on atm.

I should file that issue on github, btw. Very annoying.

https://github.com/BetterThanTomorrow/calva/issues/145

having a bit of fun here. so I had that option to chase the namespace from before. Now with the new repl when I'm in my file window, it shows that namespace, when I got back to the repl window, it goes back to user->

I think I better turn that off

That sounds like a bug, which I can’t reproduce at the moment.

But I think switching that option off is fine. I actually think we might remove it before release. The REPL window will temporarily switch namespace when you evaluate a form from a file. Which is enough of help, me thinks.

disabling it helped.

ok, I got my act together enough to actually -run- some clj code.

anything in particular you want me to check out in the new repl?

made it print a fat databall, seemed unfazed

I recmmend installing Clojure Warrior as well. It has raindbow parens and a sane highlight of current enclosing parens. Then disable vscode default matching paren highlight for clojure files (which is just weird).

already there.

Nothing in particular, no, but after having used it a while, I’d like to know what things hurt the most so that we can prioritize what to fix before release.

editing the repl line has some weird-feeling stuff.

It would be nice to see issues filed on github about the REPL window.

I can help with that

it's like the usual keys don't act as expected.

Yeah, that is a bit awkward yet.

and no history?

Some usual keys do work, some don’t. It is actually a completely new clojure editor written from scratch and hosted in a webview.

ah, that explains it.

alt+up/down for history.

jup, nice

on the history.

that's a big undertaking.

Oh, yes, would not have been possible w/o @mseddon, who’s a frontend wiz of proportions.

It really has the potential of powering lots of web based clojure editing. But we’re not opening that box up until we have it working in Calva.

is there a branch you guys are working on that I can tag along on?

But now and then I visit https://repl-interactor.netlify.com just to dream about it some.

geez, what is that thing.

It’s the REPL window frontend, basically.

Not much going on right now in development, but yes, please see the pez/repl+jack-in branch.

The jack-in functionality needs us moving the parsing of edn files into the cljs parts of the code. Might be something to take a look at.

I'm probably not understanding the intent of the line-editing in the new repl. Let's say I have "(query [:job-numbers])" in there, and I run it. Good. my next move is to alt-up and then I want to edit it to read "(count (query [:job-numbers]))" and rerun it. 'tis an all out war....

I would type (count the begonning of the line and then slurp forward. Then hit END and submit it.

Even if, truth be told, I work mostly in the files, also for such experiments. Calva will let you evaluate top level forms inside comments.

yeah, I use that too

Please take notes on things that seem awkward to you, before you get used to them.

will do

your right, you quickly learn to plow around the stumps :face_with_cowboy_hat:

That's where i am 😎