Skip to content
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

Absolute path to executable #18

Open
jmgate opened this issue Jul 10, 2023 · 0 comments
Open

Absolute path to executable #18

jmgate opened this issue Jul 10, 2023 · 0 comments
Labels
Type: Feature A new capability we need added to the code.

Comments

@jmgate
Copy link
Collaborator

jmgate commented Jul 10, 2023

Currently the get_*_command_line_invocation() methods start the command line with the executable, but it's only the name of the script being run. For replicability's sake, this should really be the absolute path to the script executed, otherwise two different users could be running scripts of the same name in different locations and they'd be different scripts, and therefore behave differently, leading to confusing that this package is intended to address.

@jmgate jmgate added the Type: Feature A new capability we need added to the code. label Jul 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Feature A new capability we need added to the code.
Projects
None yet
Development

No branches or pull requests

1 participant