I am trying to fix so that lein jack-in works on Windows with powershell. Here’s an experiment where I have simplified the quoting of the arguments. Works swell on my Mac. But I have no clue if it works on Windows with cmd.ex, nor with powershell. (My old Mac can’t handle Windows 10 in Virtual Box.) Can I get some help giving it a try. @brandon.ringe, maybe? And everyone, really, because this is a potential major break of vital functionality.

@pez with Powershell i get the exception java.lang.NumberFormatException: Invalid number: 0.6.0 and with cmd also i think the versions needs to be like thiis \"0.6.0\"

Thanks, @slack1038! I suspected that a bit. What happens in cmd.exe?

same

Interesting. Have some time to work at it together with me? It’ll be quicker than me building vsix packages blindly. 😃

yeah

Cool! I’ll PM you.

I have updated the wiki page about evaluating code. I’d like feedback. ❤️ https://github.com/BetterThanTomorrow/calva/wiki/Code-Evaluation-Tips (ping @lspector )

gentle reminder, feel free to vote on a convention for tooling (something which calva may eventually also support, if it does things like clean-ns in emacs): https://github.com/borkdude/clj-kondo/issues/241#issuecomment-500805941

Thanks @borkdude. I think I may be trying to complicate the decision here, but I proposed another alternative (`^:require/implicitly_used`) that is hopefully more intention-revealing than imperative (“keep”). 😅

thanks!

Good news! @slack1038 and I worked at this together and found a way to make jack-in work also for when powershell is the shell used by vscode. We tried for two solid hours to make nice changes that would make it work, but in the end we had to resort to a somewhat ugly workaround. Anyway, here is a build that works on both our setups. I am going to publish it soon, but am giving people here a chance to find problems before our users out there gets them. Thanks in advance for help testing this! ❤️

It works for me

@pez @slack1038 Thanks for the work. Did you make it switch the shell to cmd before running the cmd-friendly version of the command? It did ask me to allow the workspace to modify my shell (to cmd when I had it set to powershell).

It worked after I clicked allow

Yes that is the ugly workaround for now

Oh I see. Not bad though. The default PS shell is maintained

I guess the other way would be to read what shell they have set and issue the proper command for that shell?

Yes, issuing the proper command for lein.bat in powershell proved too hard for us. We could construct a command line that worked when issued in the terminal, but not when it was issued from the jack-in task.

ohh interesting

Yeah I was wondering

Several things at play together there. That's a tough one

lein seems to do something with the formatting after it takes it in. PS wants a specific format. Issuing from jack-in probably does something to it as well

I guess that when the quoting requirements of the powershell clashes with those of whatever a .bat needs it gets REALLY complicated. We do get the quoting to work for cli-deps, but that is a .ps1 script.

Is there a lein.ps1?

Don’t know.

https://github.com/technomancy/leiningen/blob/master/bin/lein.ps1

Do you have it on your machine?

The quoting for cli/deps is really complicated, by the way. Done in several steps and involves tripple backslashes and stuff. 😃

I could 🙂

oh wow

I think that if people don’t have it on their machines then it isn’t of much use for Calva.

Oh, right, duh

Have you checked on your machine?

I do not.

Installed through Chocolatey and it puts lein.bat

Interesting that they maintain it in /bin in the repo though

They also advocate the .bat on the home page installation instructions

This may be a very silly question, but can calva put lein.ps1 on someone's system during install? Like a dependency? Maybe even in a sandboxed way?

@pez

I guess it could be done. But I wonder if it’s worth it. And first we should confirm that it would help, even. 😃

Very true

Need help testing again. Added an escape out of jack-in for powershell users who do not allow the change of the setting. Ping @slack1038 and @brandon.ringe.

So to test ^ this ^ try with having both cmd.exe and powershell.exe set as shell default. And try with both allowing and not allowing Calva to change it when it needs to. I’m not sure how you reset things so that VS Code will ask again, but I hope you will figure that out. 😃

Somehow I cannot change my default shell -_-. The command won't work like it did before. I even checked the settings.json and it's set to something other than powershell when I change it, but powershell keeps being used when I open a new terminal

:thinking_face:

you migth need to change the workspace settings

That is it, thanks

Does that mean some users will still run in to troubles?

possibly I'll check if it happens again

the thing is we change the workspace settings from the code and i dont know how to do it on a global part that means if the user changes the settings globaly it wont change for the workspace itself

There is no global part. There is user and workspace. But maybe user has precedence over workspace?

It appears that workspace has precedence over user

I see what's happening

then i mean user sorry

Global is probably a good name for it. 😀 Just got to use the vscode terminology here.

So when I have powershell set as default shell in user settings (what the built-in command/task sets, and it is powershell by default on new install of vscode), then I run the jack-in command, calva is setting the workspace shell to cmd, running the jack-in command, and setting it back to powershell, but in the workspace

Then when you use the built-in change default shell task, it changes the user settings, but the workspace overrides

And is still set to powershell from Calva

So it is the restore that goes a bit wrong?

It needs to change the user setting for default shell, not the workspace, if that is possible

OR, it should remove the setting from workspace (at least if it was not there before)

https://code.visualstudio.com/api/references/vscode-api#WorkspaceConfiguration

But if the workspace had another shell set to begin with, then changing the user one would not work for calva probably

I have pushed the code to master. I must do other things right now, but if someone else can look at it, the code is there.

just as reference the link and yes this is the problem when the user changed its settings for the workspace we cant just removed it and i dont think there is a api to get the user setting and the workspace setting

*sigh*

I also don't think that api exists. Have had use for it before, but then it wasn't there.

Well at least what we have now will work for people who just installed vscode and have PS set as default

They just will have to go change workspace settings when they try to change their default shell after using the jack-in command

No big deal though

Better than it not working for a new install

oh i found a way to find out what where the terminal is set with the method inspect

nice

That gives me hope due that other feature I tried to add. 😀

😅 i cant start the compilation of calva anymore

o_O

ah now it works xD yeah i have a whacky setup xD

i just did a pull request with my improment 🙂

Can you build a package and upload here? I'm afc.

i have to go now to sport later tonight i can do it 🙂

So that is. vsce package

Ok. Maybe I'll beat you to it. 😀

@brandon.ringe can checkout your PR and build his own for testing. 😀

Have never done so but maybe I can later

Trying to get some other work done 😅

Other work? 😍

Not calva-related, unfortunately, for my living income lol

Yeah, Calva dev is for poor people, Unfortunately. Haha

Need to get Calva funded by Clojurists Together

Though being an editor extension, I don't know if it could

You could make like $3k per month for 3 months though

Fireplace got funding this time around. Just sayin'

Though my not-so-well-payed day job wouldn't allow me to go do this for three months, so it would take that someone else was ready to take the assignment.

I’m a bit tired right now, @slack1038, but it looks like you didn’t base your changes on my latest changes. I know github says there are no conflicts, but I hesitate to pull the PR since it looks like it will revert stuff…

Quite strange actually. And could just mean I should close the lid on my laptop for today.

Yeah i did something wrong But i had to make a merge because of it That is the second commit But i can also just revert my fork back and do the change again

Please do. I could probably fix it on my end, but it would be easier with a clean change.

👋

https://clojurians.slack.com/archives/CBE668G4R/p1560446670426900 disagree, I'd support this. calva oddly works perfectly for my workflow, really happy with it. especially combined with live share, remote development, etc.

just discovered it and I love cursive and friends but pretty blown away.