Talin wrote: > Ideally, you should be able to pass > "file:///..." to a regular "open" function. I'm not so sure about that. Consider that "file:///foo.bar" is a valid relative pathname on Unix to a file called "foo.bar" in a directory called "file:". That's not to say there shouldn't be a function available that understands it, but I wouldn't want it built into all functions that take pathnames. -- Greg
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4