search

schell / steeloverseer

A file watcher and development tool.
BSD 3-Clause "New" or "Revised" License
128 stars 15 forks source link

Special case for working on a single file script #24

Open ethercrow opened 7 years ago

ethercrow commented 7 years ago

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.

schell commented 7 years ago

I'm a bit overwhelmed with work at the moment, but I would accept a PR for this feature ;)

mitchellwrosen commented 7 years ago

I assume you'd (always?) rather run ./file when file is touched, in case . is not in your PATH.

schell commented 7 years ago

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?

ethercrow commented 7 years ago

No, only repetition. I could easily make a shell shorthand sos1 for this, so no worries.

mitchellwrosen commented 7 years ago

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 :)