Can you make a minimal reproduction of this? It’s very cryptic, indeed.

Are you running in a dev container or against a remote repo (or both)? I’ve seen something similar, don’t remember exactly what, when running against a dev container over SSH.

No, I was running locally. I ended nuking every process running Node closing the project and opening again.

I think I figure it out. Ctrl + Shift + P.

@U0ETXRFEW @U9A1RLFNV Is that something that could get added into the docs? It took me about 10 minutes to figure that out.

Definitely! Thanks for calling that out.

OK, I see I can get there via "View" > "Command Palette" too.

I just found that myself 😄

Docs are updated

Nice! Thanks!

Thanks for highlighting this need for better documentation, @U5FV4MJHG ! I’m not sure writing out how to open the command palette here is the right solution. It’s giving the hungry man a fish instead of teaching him how to fish. 😀 The general approach I’ve been trying to follow is that VS Code knowledge is somewhat out of scope for the Calva docs. I’ve been trying to defer to guides for getting started with VS Code out there. In fact we do so on this very page, at the beginning. There’s also a page about finding Calva commands, in the Start Here main menu of the site. https://calva.io/finding-commands/ Though, of course we should expect readers of the site to be in skim mode until some action happens, so relying on some introductory notes does not suffice. It’s seems to me that this place in the article, where the action starts, is a good spot to insert some pointers about where to find info about VS Code, and also about that page about finding Calva commands. Possibly we should also build out that page a bit around more VS Code things that are important for Calva usage. Whatever that might be.

Glad the way to open this particular menu is in VS Code's getting-started now. Better for someone to become annoyed with VS Code after they're hooked on Calva, than before.

@U0ETXRFEW Thanks for the feedback. I understand that you don't want to repeat a bunch of VS Code docs, but at the very least, it would be helpful to mention the name "command palette". Because I didn't know what to search for, it was a lot harder for me to figure out what to do. I had no idea there was such a thing as a "command palette". Just to give you an idea of the nature of the obstacle, here are the steps I went through to figure it out... I think my first Google search was "how to open search box in VS Code" and that did not give me the "command palette". My next step was to watch the video "Getting started with Visual Studio Code", and I somehow missed the bit about the command palette. It's about 5 seconds long, over a minute into the video, and not on a chapter marker. My next step was to start watching your video "https://www.youtube.com/watch?v=O6GrXXhCzCc&t=30s". You bring the command palette up at second 30, but it's with a hotkey and you don't mention the name "command palette". After that, I started googling "VS Code User Interface" and I came across https://code.visualstudio.com/docs/getstarted/userinterface doc. I scrolled through it until I saw a screenshot that looked like the "search box" from the docs and that's when I figured it it was called the "command palette". Mentioning "command palette" would help a ton, and beyond that, I can understand if you don't want to repeat much that's documented elsewhere.

That makes perfect sense, @U5FV4MJHG. We mention command palette a lot on the site, but have somehow missed it in the most important place.

@U0ETXRFEW Thanks! I know you and @U9A1RLFNV do a ton of work. Thanks again!

I think at least some small amount of redundancy of helpful information, at points where it's relevant, is good for documentation and reduces the need for the reader to bounce around the docs / context switch. For lengthier explanations, though, linking to them from the relevant locations would be good.

F1 also works, @U5FV4MJHG, which might be more convenient for you depending on your keyboard.

Just chiming in to agree that while it's totally reasonable to leave any detailed VSCode instructions to the VSCode docs, it can be super helpful to beginners to provide at least minimal orientation. We are fortunate that this can be so brief here, probably just mentioning the existence of the Command Palette and how to get to it. For this, I'd recommend not a key command but rather View > Command Palette since I think that's system independent and understandable by all. We are also fortunate (or rather, I should say we should be thankful to the Calva developers!) that so much of Calva's functionality can be discovered by typing "calva" into the Command Palette search field. This would also be a great thing to mention early in any instructions for beginners.

> For this, I'd recommend not a key command but rather View > Command Palette since I think that's system independent and understandable by all. This is what the docs say now > If you are new to Calva, a good place to start is using the command Fire up the ”Getting Started” REPL. (You can open the command palette using the VS Code top menu by going to View -> Command Palette... or by running the associated keyboard shortcut for your OS.)