Hello. This is the standard procedure for jack-in, except you don’t need to have nrepl as an extra dep since the jack-in command will inject it for you.

I noticed in the main thread you said: > This worked when the underlying project was created with leiningen. But now in a non leiningen project the behavior is not the same. Are you having some issue with a deps project?

I would not call it issues but rather lack of knowledge 😄. I had the impression that calva itself lead me to performing these steps. As far as I can tell it did work. The "project" consists of a deps.edn file and clj file. I assume that jacking-in in a leiningen project is more streamlined than just a deps.edn + clj file 🙂

If there’s anything you think could be improved, please let us know.

I am very happy with calva as it is and that I have the possibility to use it 😀! Thx!

Glad to hear!

@UKFSJSM38 Is there anything related to clojure-lsp that Calva could not support before (easily) unless we updated vscode-languageclient?

I don't recall of anything @U9A1RLFNV

Hello! I was running into errors with my development environment. Basically, clojure-lsp wouldn't start up at all in my VSCode; I'd click "Start the clojure-lsp server" and nothing would happen. After fiddling with clojure-lsp for a while, I saw this post and tried downgrading Calva to the previous patch, which solved my problem. I'm not well-enough acquainted with Calva to give more insight to where the issue might lie

@U03HHFSUF7F could you share your calva startup window output? like version and OS info

Welcome to Calva. Happy Clojure and ClojureScript coding! ❤️

Please check these resources out:
  Calva Documentation: 
  #calva at the Clojurians Slack: 
  Bug reports: 

If you like Calva, please consider how you can contribute: 

Calva is utilizing cider-nrepl and clojure-lsp to create this VS Code experience.
  nREPL dependencies configured:
    nrepl: 0.9.0
    cider-nrepl: 0.28.5
    cider/piggieback: 0.5.3
  clojure-lsp version configured: 2022.06.29-19.32.13

If you are new to Calva, please consider starting with the command:
  **Calva: Fire up the Getting Started REPL**
  

(See `showCalvaSaysOnStart` in Settings to control the auto-showing of this message panel.)

(this is with the issue)

macOs Monterey, version 12.4

It seems it's not using latest clojure-lsp

Ah you're right; I downgraded that myself in settings.json earlier when I was trying to debug the issue. With the following output, the issue still manifests:

Welcome to Calva. Happy Clojure and ClojureScript coding! ❤️

Please check these resources out:
  Calva Documentation: 
  #calva at the Clojurians Slack: 
  Bug reports: 

If you like Calva, please consider how you can contribute: 

Calva is utilizing cider-nrepl and clojure-lsp to create this VS Code experience.
  nREPL dependencies configured:
    nrepl: 0.9.0
    cider-nrepl: 0.28.5
    cider/piggieback: 0.5.3
  clojure-lsp version configured: latest

If you are new to Calva, please consider starting with the command:
  **Calva: Fire up the Getting Started REPL**
  

(See `showCalvaSaysOnStart` in Settings to control the auto-showing of this message panel.)

c/c @U9A1RLFNV

@U03HHFSUF7F Do you see any errors in the developer console? Help -> Toggle Developer Tools -> Console tab.

Also, do you see any message or any indication that clojure-lsp didn’t start, besides in the status bar at the bottom?

Thanks for the help troubleshooting! The language client requires VS Code version ^1.67.0 but received version 1.66.0 is coming up a lot in the console

> Also, do you see any message or any indication that clojure-lsp didn’t start, besides in the status bar at the bottom? I didn't see any messages per se—no pop-ups, no toasts, nothing I could see directly. My indication that it wasn't working was the status-bar and the fact that I couldn't e.g. command-click functions to jump to their definitions

Oh, hmm. I have an idea of how to fix that.

What’s your version of VS Code, btw?

Can you install this vsix and let me know if you still have the issue with it? https://output.circle-artifacts.com/output/job/2aef0b6c-aa17-4d85-8ed1-8ba883ff7ec5/artifacts/0/tmp/artifacts/calva-2.0.291-fix-clojure-lsp-start-issue-7e98cd75.vsix

Version: 1.66.0 (Universal)
Commit: e18005f0f1b33c29e81d732535d8c0e47cafb0b5
Date: 2022-03-30T05:50:04.419Z (4 mos ago)
Electron: 17.2.0
Chromium: 98.0.4758.109
Node.js: 16.13.0
V8: 9.8.177.11-electron.0
OS: Darwin arm64 21.5.0

@U9A1RLFNV Beginner question maybe, but how do I apply this VSIX file? When I download it, it's a zip file that unzips into a directory. When I go (Extension Pane > Meatball Menu > Install from VSIX), there's nothing valid for me to select

Select the zip file, then hit command+i, then edit the extension to replace .zip with .vsix.

Then you can use the VS Code command to install the vsix.

There may be a better way to do the extension change but that’s how I do it.

I’m beginning to suspect you’ll need to update VS Code..

Ah okay, I had been trying just to rename the file. This little toast pops up; I didn't realize I was running such an outdated version

Oh, glad it explains that to you.

Let me know if it works after you update.

I’m hoping there aren’t many people on versions < 1.67

Bringing VSCode up to 1.69.2 resolved my issues with the latest Calva patch :thumbsup: Thanks for the help! Much appreciated

Awesome! I’ll push out a new version soon.