We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
On Unix, some programs run other programs. It is standard convention to pass along the tail of the command line unprocessed.
Examples:
bash -c command [args] time command [args] schedtool -e command [args] chroot /newroot command [args]
The text was updated successfully, but these errors were encountered:
cc @nick29581, could this be migrated to https://github.com/rust-lang/getopts?
Sorry, something went wrong.
This issue has been moved to the RFCs repo: rust-lang/getopts#6
Auto merge of rust-lang#12306 - Alexendoo:dir-replacement, r=flip1995
74f611f
Remove `$DIR` replacement This won't cause problems because the old `$DIR` replacement was based on the parent of the test path, which for us is relative: https://github.com/rust-lang/rust-clippy/blob/5471e0645a497ab331ae38adc965aa15b74aa8c9/tests/compile-test.rs#L122 The new pattern being `"tests/{test_dir}"` is more clearly relative That's why we have custom filters applied to the toml/cargo tests where absolute paths do appear in the output https://github.com/rust-lang/rust-clippy/blob/5471e0645a497ab331ae38adc965aa15b74aa8c9/tests/compile-test.rs#L198-L202 Removing it allows clicking the paths in the terminal changelog: none r? `@flip1995`
No branches or pull requests
On Unix, some programs run other programs. It is standard convention to pass along the tail of the command line unprocessed.
Examples:
The text was updated successfully, but these errors were encountered: