Debian Bug report logs - #787557
exo-utils: exo-open seems confused by escaped characters in URL's

Reply or subscribe to this bug.

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Luis Mochan <mochan@fis.unam.mx>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: exo-utils: exo-open seems confused by escaped characters in URL's

Date: Tue, 02 Jun 2015 13:10:20 -0500

Package: exo-utils
Version: 0.10.6-1
Severity: normal

Dear Maintainer,

With exo-open I can open a file or directory with embedded spaces using a
command like

  exo-open 'A B'
  exo-open 'A\ B'
or
  exo-open 'file:/home/user/A B'
but I can't open the file using URL escaped characters as in
  exo-open 'file:/home/user/A%20B'
I found this problem while using Calibre, as it replaces spaces by %20's before
opening files. I'm sorry I'm not sure if this is Calibre's fault or exo-open's
fault.

Thanks,
Luis




-- System Information:
Debian Release: stretch/sid
  APT prefers testing-updates
  APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages exo-utils depends on:
ii  libc6               2.19-18
ii  libexo-1-0          0.10.6-1
ii  libgdk-pixbuf2.0-0  2.31.4-2
ii  libglib2.0-0        2.44.1-1
ii  libgtk2.0-0         2.24.25-3
ii  libxfce4ui-1-0      4.12.1-2
ii  libxfce4util7       4.12.1-2

exo-utils recommends no packages.

exo-utils suggests no packages.

-- no debconf information

Message #10 received at 787557@bugs.debian.org (full text, mbox, reply):

From: Luis Mochan <mochan@fis.unam.mx>

To: 787557@bugs.debian.org

Subject: update

Date: Tue, 16 Jun 2015 13:17:20 -0500

I made some more tests.
I can open a file named 'A B' (with a space in its name) using 
 1  exo-open 'A B'
or
 2  exo-open A\ B
I can also open it with thunar using
 3  thunar 'A B' 
or 
 4  thunar A\ B
I can not open it using and URI as in
 5  exo-open file:A\ B
nor can I open it with
 6  thunar file:A\ B
In case 5 above there is an error message from thunar, unable to open 
the file A%20B. So the translation space->%20 seems to be done by 
exo-open before calling thunar.
Nevertheless, if I use the full path, not relative paths, both commands 
succeed:
 7  exo-open file:/home/user/A\ B
but I can open it with thunar with the same syntax
 8  thunar file:/home/user/A\ B
It confuses me that if I introduce the escaped space by hand,
 9  exo-open file:/home/user/A%20B
 10  thunar file:///home/user/A%20B

the call 9 to exo-open fails but the call 10 to thunar does succeed. 
Could it be that exo-open is escaping the '%''s? Finally, the call
 11 thunar file:A%20B
fails.

In conclusion, it seems that exo-open fails when it is handed a URI with 
spaces replaced by %20. 

My problem is that calibre uses exo-open and makes the replacement 
before calling it. I'm made up an ugly solution: I put in my path a fake 
exo-open that replaces back %20's to spaces before calling the real 
exo-open.

Regards,
Luis




  

-- 

                                                                  o
W. Luis Mochán,                      | tel:(52)(777)329-1734     /<(*)
Instituto de Ciencias Físicas, UNAM  | fax:(52)(777)317-5388     `>/   /\
Apdo. Postal 48-3, 62251             |                           (*)/\/  \
Cuernavaca, Morelos, México          | mochan@fis.unam.mx   /\_/\__/
GPG: 791EB9EB, C949 3F81 6D9B 1191 9A16  C2DF 5F0A C52B 791E B9EB

Send a report that this bug log contains spam.