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

Quickrun and Quickrun-Shell have differing environments because of eshell #106

Open
michaelbartnett opened this issue Nov 21, 2019 · 0 comments

Comments

@michaelbartnett
Copy link

Quickrun-shell is the way to enable stdin when running a file, but the way it does this is via eshell, which doesn't load the standard environment.

For example, this means if you use something like pyenv to manage python installations, quickrun and quickrun-shell will run two different versions of python.

Afaik eshell explicitly does not try to load bash profiles or anything like that, so there's no real way to make this work with eshell.

But what you can do, however, is instead of using eshell, use compilation-start and pass t to put it in interactive mode.

I'm not sure if you can get the "press R to restart" behavior with comint mode, but I'd much rather have stdin and consistent environments than the ability to rerun with a single key. That's what M-x repeat-command is for 😛

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

No branches or pull requests

1 participant