Improve error message when there's a colon in the project directory name

[minijackson]

Steps to reproduce:

• cargo new bla
• mv bla "bla:"
• cd "bla:"
• cargo test --verbose

Error:

error: failed to join search paths together: path segment contains separator `:`
Does $LD_LIBRARY_PATH have an unterminated quote character?

Caused by:
  failed to join path array: ["/tmp/bla:/target/debug/deps", "/home/minijackson/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib"]

As LD_LIBRARY_PATH is a Unix thingy, I don't know if it is reproducible in Windows ;-)

Meta:

cargo 0.18.0-nightly (56083a3 2017-02-18)
release: 0.18.0
commit-hash: 56083a3362999695193a8f2252d17b0e4c32145e
commit-date: 2017-02-18

[alexcrichton]

IIRC a colon is an illegal character in a path on Windows, but we probably shouldn't fail like this on Unix.

[cyplo]

Would it be worth promoting this issue as beginner-friendly ?

[alexcrichton]

Ah no unfortunately I don't think this'll be easy to fix, all we can really do is probably provide a better error message :(

[stale]

As there hasn't been any activity here in over 6 months I've marked this as stale and if no further activity happens for 7 days I will close it.

I'm a bot so this may be in error! If this issue should remain open, could someone (the author, a team member, or any interested party) please comment to that effect?

The team would be especially grateful if such a comment included details such as:

• Is this still relevant?
• If so, what is blocking it?
• Is it known what could be done to help move this forward?

Thank you for contributing!

(The cargo team is currently evaluating the use of Stale bot, and using #6035 as the tracking issue to gather feedback.)

If you're reading this comment from the distant future, fear not if this was closed automatically. If you believe it's still an issue please leave a comment and a team member can reopen this issue. Opening a new issue is also acceptable!

[stale]

As I didn't see any updates in 30 days I'm going to close this. Please see the previous comment for more information!

[grunweg]

I just ran into this issue:
while a search for "path segment contains separator" found this issue quickly, being told about the cause (colons in the directory name) would have made this easier.

[ehuss]

I can reopen, adding a better error message probably shouldn't be too difficult.