Developers cannot scope shell helpers to individual projects
Developers want project-specific command completions, aliases, and functions to appear when they enter a repository and disappear when they leave. The signals describe gaps in directory-based environment workflows: users keep separate shell hooks, enable completions globally, or face an inconvenient installation path. These requests are historical, so the current state of the tools should be checked before building.
For developers using project-specific command-line tools. Mentioned from Mar 2015 to Jun 2020 on GitHub.
5 different people described this problem in 2 separate discussions.
- Indie fit
- 3.0/10
- Pain
- 5.2/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.
At work we have python-based CLIs in our repos, and being able to auto-activate their virtualenvs and add their shell completions when cd'ing into a repo without permanently polluting the environment would make using the CLIs much, much easier
I was exactly looking for this feature. For example I use awscli which requires complete -C awscompleter aws but I do not want to have enabled for the system because my awscli` is installed in specific virtualenv
Build brief
See what to build and who will buy it
- 1 product idea with the smallest useful version and pricing
- 3 places to find your first customers
- 3 more quotes from people who have this problem
- Current workarounds, existing solutions and risks