-
Notifications
You must be signed in to change notification settings - Fork 5
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
pipeline ignores shell initialization routines #5
Comments
Agreed that'd be a nice addition. Most common shells support the I think we'd have to make them login shells too in order to load user aliases/functions -- bash has the Tab completion wouldn't work with the custom aliases and functions, I think we're kind of stuck there with the current implementation. |
I had a use-case for using a |
Whoops, I meant "interactive shell" everywhere that I said "login shell" above. I've tested using an interactive shell in bash, zsh and fish and everything seems to work well. So this will now allow using custom aliases and functions etc, though as I mentioned above it won't autocomplete them -- I really don't know how we could make that work without integrating pipeline directly into the shell itself (which I would love to see happen someday). |
I celebrated too soon -- with further usage I'm seeing an intermittent issue with interactive shells and zsh (haven't tested other shells yet). Sometimes, but not always, it prints |
Things like custom aliases and functions are not available in the pipeline.
This is what is problematic with current approach of hardcoding
/bin/sh
instead of using current shell. Not sure if the real shell can be used instead?The text was updated successfully, but these errors were encountered: