<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - Unnecessary filtering file:// for pcmanfm" href="https://bugs.freedesktop.org/show_bug.cgi?id=63153#c5">Comment # 5</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - Unnecessary filtering file:// for pcmanfm" href="https://bugs.freedesktop.org/show_bug.cgi?id=63153">bug 63153</a> from <a class="email" href="mailto:david.costa@ieee.org" title="David Costa <david.costa@ieee.org>"> David Costa</a> <pre>Created <a href="attachment.cgi?id=101704" name="attach_101704" title="Followup of 0001-xdg-open-fixes-63153-keeping-the-path-as-URL.patch">attachment 101704</a> <a href="attachment.cgi?id=101704&action=edit" title="Followup of 0001-xdg-open-fixes-63153-keeping-the-path-as-URL.patch">[details]</a> <a href='page.cgi?id=splinter.html&bug=63153&attachment=101704'>[review]</a> Followup of 0001-xdg-open-fixes-63153-keeping-the-path-as-URL.patch With the previous patch file:// URLs with relative paths are expanded in the wrong way. This patch fixes it and must be applied after 0001-xdg-open-fixes-63153-keeping-the-path-as-URL.patch File URLs are described in RFC 1738, section 3.10 but it's not clear if relative paths are possible or not. xdg-open assumes it is possible so the new patch appends the current working directory between file:// and the rest in order to make it an absolute path. That's just the same old behavior applied to a file:// URL</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>