Terminal only wants to open settings.json in Microsoft Visual Studio #19368

Open
opened 2026-01-31 06:41:16 +00:00 by claunia · 0 comments
Owner

Originally created by @caitp on GitHub (Feb 11, 2023).

Originally assigned to: @DHowett on GitHub.

Windows Terminal version

whatever it is

Windows build number

who cares

Other Software

No response

Steps to reproduce

  1. Click this
    image

  2. Encounter this
    image

  3. See if the EDITOR environment variable is honoured

  4. It isn't

  5. Look for an option in the terminal settings

  6. Can't find one

  7. Use a search engine to figure out if there's supposed to be some registry key or something that you can alter

  8. At this point, you quickly lose patience because finding anything online is pretty much hopeless because search engines have been getting consistently less useful every year for at least a decade if not longer.

  9. Ask the chatbot, who tries to be helpful but kind of isn't
    image

  10. Obviously this isn't where settings.json actually is, the file does not exist, it's probably somewhere around there but fuck man, why not just do things the normal and expected way so that stuff is less painful to use?

Expected Behavior

Use an environment variable, or a consistent configuration mechanic that's greppable and possible to find things in, and have a user interface interaction that makes this easy to accomplish with instructions your grandma can figure out just by reading and following the visual direction of the window presentation.

Actual Behavior

It's a mystery

Originally created by @caitp on GitHub (Feb 11, 2023). Originally assigned to: @DHowett on GitHub. ### Windows Terminal version whatever it is ### Windows build number who cares ### Other Software _No response_ ### Steps to reproduce 1) Click this ![image](https://user-images.githubusercontent.com/2294695/218270889-dd68d1b0-2b97-4e62-b770-d5b75817a0b3.png) 2) Encounter this ![image](https://user-images.githubusercontent.com/2294695/218270938-c9ee2385-9c6c-4362-8c1f-bb8d6746f68a.png) 3) See if the EDITOR environment variable is honoured 4) It isn't 5) Look for an option in the terminal settings 6) Can't find one 7) Use a search engine to figure out if there's supposed to be some registry key or something that you can alter 8) At this point, you quickly lose patience because finding anything online is pretty much hopeless because search engines have been getting consistently less useful every year for at least a decade if not longer. 9) Ask the chatbot, who tries to be helpful but kind of isn't ![image](https://user-images.githubusercontent.com/2294695/218271216-301d2c43-254e-4a25-9233-18e8379fb5e5.png) 10) Obviously this isn't where settings.json actually is, the file does not exist, it's probably somewhere around there but fuck man, why not just do things the normal and expected way so that stuff is less painful to use? ### Expected Behavior Use an environment variable, or a consistent configuration mechanic that's greppable and possible to find things in, and have a user interface interaction that makes this easy to accomplish with instructions your grandma can figure out just by reading and following the visual direction of the window presentation. ### Actual Behavior It's a mystery
claunia added the Issue-QuestionNeeds-TriageIssue-BugResolution-Answered labels 2026-01-31 06:41:17 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#19368