-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Release cargo/src/cargo/util/shell_escape.rs independently #3374
Comments
Seems fine to me! I may not get around to this soon but if someone else would like to do so I wouldn't mind adding a dep to Cargo. |
@alexcrichton Should this live in this repo or can I just yank it into a new one? |
@sfackler be my guest! |
sfackler
added a commit
to sfackler/cargo
that referenced
this issue
Dec 30, 2016
bors
added a commit
that referenced
this issue
Dec 30, 2016
Use externally sourced shell-escape Closes #3374 r? @alexcrichton
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'd love to be able to use shell escapes in contexts other than Cargo.
I'm using a a copy of an old version of that file in Thrussh, when doing an ssh exec request, which is a remote command without opening a shell.
How about a shell_escape crate, which would be used by Cargo instead of this file?
The text was updated successfully, but these errors were encountered: