-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Run shell functions #46
base: master
Are you sure you want to change the base?
Conversation
# off we go | ||
os.execvpe(command[0], command, env) | ||
# Is it a shell function? | ||
if ( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we should follow the semantics of shell functions in that they override items in the $PATH
, rather than only being called if they don't exist.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah right, so swap the two checks?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Indeed
|
||
# off we go | ||
os.execvpe(command[0], command, env) | ||
print('Could not find "{}" in your procfile or $PATH.'.format(command[0])) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Worth mentioning here about it also not being a shell function?
Although that would be quite a long message. Shells just do "command not found".
Before:
After: