Mike, you're right, I did not escape the colon in a way that changes what the program gets. I just tried that, it doesn't matter.
There are, of course, ways of entering the filename in a way that makes evince (or other GNOME) programs be able to open them. One can enter the path in a way to have a slash before the colon (./foo:bar.pdf) or even a file:// url. However, the documentation (manpage, --help) claims that evince accepts filenames and that is clearly wrong. Evince accepts more than just filenames, and some valid filenames are interepreted wrongly. This can be fixed via, for example, fixing the documentation to clearly say that the programs accept filenames or URLs. This, at least, would make it obvious to the user that the colon may be a problem. (I'm also having a hard time seeing why this bug is incomplete, fixing that...) -- evince has trouble handling filename with escaped shell characters https://bugs.launchpad.net/bugs/160996 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
