Message162171
I agree that chr(32) should be included in FILENAME_CHARS.
The algorithm for backward searching checks that each character is contained in FILENAME_CHARS. I'm concerned about running time, as expanding FILENAME_CHARS to include all valid Unicode would be a large set to search. Do you know a better algorithm for determining when to perform a file-system completion when in a string?
Also, are there any Unicode code points above 127 that are not valid in a filename? I appreciate that different file systems can have different constraints but I don't know all these subtle points. |
|
Date |
User |
Action |
Args |
2012-06-02 20:03:52 | roger.serwy | set | recipients:
+ roger.serwy, loewis, terry.reedy, westley.martinez, fgracia |
2012-06-02 20:03:52 | roger.serwy | set | messageid: <1338667432.42.0.321977088145.issue14937@psf.upfronthosting.co.za> |
2012-06-02 20:03:51 | roger.serwy | link | issue14937 messages |
2012-06-02 20:03:51 | roger.serwy | create | |
|