using --manifest-path is not user friendly #1823
dirkpetersen
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
There have been a few discussions about a pixi project not being CWD and the usability issues with that. Those 2 threads bring up various aspects
#1021
#1444
but I just want to point out what the core issue is for me. My data is NEVER inside a pixi project and pathwise most likely quite far away from it, so when I create a new pixi project, one of the first things I want to do is :
The last command would be very useful when I re-enter an existing project while working on some datasets with different environments e.g. different versions of software but it seems my workflow is either
or i have to enter a command line monstrosity such as
I have done this like 20 times, and each time I go back and read the help I realize I have to enter a --manifest-path. Also I have no idea or interest what a pixi.toml file is so I think Pixi should just really take a project path,
especially since there seems to be no first command line argument for the pixi shell command anyway
Some folks mention that users have difficulties remembering the path their project is in. This is true and it has been a problem for 40 years and it can be addressed through add-on functionality or external tools but the most simple use cases should be supported without me having to think about it. I am 'only' using
pixi init
,pixi add/remove
andpixi shell
.Otherwise Pixi is the greatest thing since sliced bread, of course!
Beta Was this translation helpful? Give feedback.
All reactions