steeloverseer
steeloverseer copied to clipboard
Special case for working on a single file script
When I'm working on a script named "foo.py", I'd like to use sos foo.py as a shorthand for sos foo.py -c foo.py. The former invocation does nothing, so this change should not break anything.
I'm a bit overwhelmed with work at the moment, but I would accept a PR for this feature ;)
I assume you'd (always?) rather run ./file when file is touched, in case . is not in your PATH.
I'm not so sure about this request as it saves only a little typing. @ethercrow is there any other reason you prefer not to write foo.py -c ./foo.py?
No, only repetition. I could easily make a shell shorthand sos1 for this, so no worries.
I'm slightly in favor, as you're right it doesn't clash with any syntax. Currently, running sos without any -c arguments (and no yaml file) is basically a mistake :)