Tilde expand windows paths with backward slashes

[mjptree]

The following tilde expansion check is insufficient on windows if the input path uses backslash notation:

shellexpand/src/lib.rs

Lines 665 to 690 in e707d07

	pub fn tilde_with_context<SI: ?Sized, P, HD>(input: &SI, home_dir: HD) -> Cow<str>
	where
	SI: AsRef<str>,
	P: AsRef<Path>,
	HD: FnOnce() -> Option<P>,
	{
	let input_str = input.as_ref();
	if input_str.starts_with("~") {
	let input_after_tilde = &input_str[1..];
	if input_after_tilde.is_empty() || input_after_tilde.starts_with("/") {
	if let Some(hd) = home_dir() {
	let result = format!("{}{}", hd.as_ref().display(), input_after_tilde);
	result.into()
	} else {
	// home dir is not available
	input_str.into()
	}
	} else {
	// we cannot handle `~otheruser/` paths yet
	input_str.into()
	}
	} else {
	// input doesn't start with tilde
	input_str.into()
	}
	}

Specifically the test:

        if input_after_tilde.is_empty() || input_after_tilde.starts_with("/") {

The path "~/.cargo" e.g. would expand correctly, however "~\\.cargo" would fail to expand correctly.

[ijackson]

Hi. As discussed in #17 I am taking over maintenance of this crate. The new repository is here: https://gitlab.com/ijackson/rust-shellexpand

I think I agree with this bug report. I have reproduced it here https://gitlab.com/ijackson/rust-shellexpand/-/issues/4 in the new repo. I'm afraid I don't have time to fix it right now but I would welcome an MR.

[Trolldemorted]

Hi. As discussed in #17 I am taking over maintenance of this crate. The new repository is here: https://gitlab.com/ijackson/rust-shellexpand

this should really go into the readme