Clojurians Log v2
calva 2025-04-15
Dear Calva friends: https://github.com/BetterThanTomorrow/calva/releases/tag/v2.0.501 • Fix: https://github.com/BetterThanTomorrow/calva/issues/2780 • Fix: https://github.com/BetterThanTomorrow/calva/issues/2785 Again it’s @phill providing. And, by extension, @weavejester. Thanks! 🙏 ❤️ calva
Help needed. VS Code all of a sudden opens all files in a new editor group. I have always had it opening files in the active group, and this new behaviour drives me crazy. I don’t know if it is a bug in latest VS Code, or if I have happened to fat finger in some bad configuration or what is going on. Insiders behaves like I am used to. Anyone have any idea? Both Copilot and Grok think the best idea is to reformat the hard drive and reinstall everything from scratch.
I think I solved it. Somehow what was listed as Group 1 by VS Code seems to have been some mystery Group 0. When opening a file it opened in the real Group 1. I got rid of it by closing all files in Group 0 and then closing the group. Let’s hope that was the end of it. I didn’t know an editor could get under my skin like that.
Glad it sounds like you solved it @pez! Hope that's the end of it. I just installed the VSCode update and my editor seems to be behaving normally.
When my repl startup script launches a portal view and terminal as tab, the group is locked for some reason. Then behavior can be wierd, and definitely files open in other groups.
Ah, so I had a stale output terminal as a tab in that group. Maybe that’s the repro!