Project environments break across shells, editors, and tasks
Developers working across projects want each project’s environment settings to follow them into shells, editor processes, workspace paths, and tasks. The signals describe gaps in passing or undoing those settings, which can make switching projects clunky or require workarounds. A small tool could help, but the requests span several editors and environment managers, and some evidence is several years old.
For developers working across multiple projects and IDEs. Mentioned from Jun 2014 to Jun 2024 on GitHub and Hacker News.
5 different people described this problem in 5 separate discussions.
- Indie fit
- 5.0/10
- Pain
- 5.6/10
- Frequency
- 6.5/10
- Willingness to pay
- 0.0/10
- Momentum
- 5.0/10
- Who pays
- Professionals
- Competition
- Medium
- Build difficulty
- Medium
What people said
Quoted word for word. Follow a link to read the whole discussion.
It works, but is nothing but a big hack (because the JVM does not want you to modify the environment...). To natively support changing the environment on a per project basis, the IDE could clone the environment from the OS (like the JVM does it) and pass the clone to all processes it launches while allowing modificatio…
It's definitely clunky and tedious to switch between every projects or scripts environment
tayo42 on Hacker NewsJun 2024
Build brief
See what to build and who will buy it
- 2 product ideas with the smallest useful version and pricing
- 5 places to find your first customers
- 3 more quotes from people who have this problem
- Current workarounds, existing solutions and risks