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

source command not working #94

Closed
Harsh-0-7 opened this issue Jul 9, 2024 · 3 comments
Closed

source command not working #94

Harsh-0-7 opened this issue Jul 9, 2024 · 3 comments

Comments

@Harsh-0-7
Copy link

not working source environ.txt
image

It is working fine if we type command source environ.txt and run. But when i save in keep and run. It gives error.

@rahuliyer95
Copy link
Collaborator

rahuliyer95 commented Jul 9, 2024

Similar to #57 #75 #87, keep commands run in a subshell that gets erased after the command is complete. This is the reason your source command cannot work with keep.

@Harsh-0-7
Copy link
Author

Harsh-0-7 commented Jul 9, 2024

@rahuliyer95 Thanks for the explanation.
I am just wondering, can't we add option to run command in shell and in subshell?

@rahuliyer95
Copy link
Collaborator

@rahuliyer95 Thanks for the explanation. I am just wondering, can't we add option to run command in shell and in subshell?

From #57

This Q&A on stackoverflow says that it is not possible to use the export command as it is from Python. So, perhaps keep should give out a warning that export command will not work from Python or there may be a workaround to it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants