Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upStick to Windows-friendly filenames #4627
Comments
|
Hmm. The question mark is useful because it allows for an automated test using a query string. Maybe we just need a test harness annotation instead. |
|
This makes git clone on Windows report the following error when checking out: error: Invalid path 'tests/ref/hello_a?foo#bar.html' The following article talks about allowed characters in Windows paths: link. To recap:
Fixing this will also fix issue #3911. |
|
I guess we should just take the "#bar" out of the filename and update the entry in basic.lit to match. |
|
Well, the whole "?foo#bar.html" needs to be taken out because of the question mark. |
|
Ah right. I guess we don't get to have an automated test for #3340 :( |
|
We can have mach create the file based on your OS :) |
|
Wait, we'd still need special harness code to make that work. Hmm. |
|
I just noticed "%" is allowed on Windows. If that's possible on other platforms as well, maybe we could encode special characters like done with the URLs? Like %3F for "?"? |
|
But the test is explicitly for testing the opening of a file with a ? in its name :) |
|
Ouch! Then I guess conditionally creating it depending on the OS is the best bet :) |
|
Though it’s not great, I’d say it’s acceptable to remove |
|
I don't know how the |
|
You could perhaps filter filenames for |
|
Sorry, didn't explore thoroughly and don't know the test harness, but @Manishearth do you mean it would be hard to generate the file for a test only on |
|
Fixed by #7610. |
e.g. The question mark in
hello_a?foo#bar.htmlis reported to cause problems. We also had issues withaux.rsin the past.We should figure out the exact rules, then enforce them in
tidy.py.