Page 1 of 1

Problem with torrent's path

Posted: Sat Apr 23, 2016 3:54 pm
by Joe96
Hey, i am using a command similar to this:

Code: Select all

deluge-console add -p 'D:\TV Shows\The Big Bang Theory' 'C:\Users\Joe\Desktop\The.Big.Bang.Theory.S09E01.720p.HDTV.X264-DIMENSION.torrent'
and the response is

Code: Select all

Attempting to add torrent: C:\\Users\\Joe\\Desktop\\The.Big.Bang.Theory.S09E01.720p.HDTV.X264-DIMENSION.torrent
Torrent added!
But my problem is that the torrent doesn't download due to this error:

Code: Select all

The filename, directory name, or volume label syntax is incorrect: D:\\TV Shows\\The Big Bang Theory\The.Big.Bang.Theory.S09E01.720p.HDTV.X264-DIMENSION\The.Big.Bang.Theory.S09E01.720p.HDTV.X264-DIMENSION.mkv
Is it my fault, or deluge's?

Re: Problem with torrent's path

Posted: Sat Apr 23, 2016 5:45 pm
by Cas
Honestly not sure, although there does seem to be a path inconsistency there in the error output. It loads the torrent then? What is the download path in gtkui? If you manually change it does it work?

Re: Problem with torrent's path

Posted: Sat Apr 23, 2016 10:11 pm
by Joe96
Cas wrote:Honestly not sure, although there does seem to be a path inconsistency there in the error output. It loads the torrent then? What is the download path in gtkui? If you manually change it does it work?
The torrent loads, and if i change the path manually it does download. The problem is that i use quotes to escape the whitespaces in the path, but doing that sends the string

Code: Select all

D:\\TV Shows\\The Big Bang Theory
as the download location. The problem is that windows doesn't recognise the "\\", therefore, deluge sees it as an invalid path. All that needs to be done is to get rid of the double slashes. The problem is i do not know how to do that. Any tips?

EDIT:
Also, if i try to use a path that has no white spaces in it, and is not escaped, it successfully starts downloading

Re: Problem with torrent's path

Posted: Sat Apr 23, 2016 10:36 pm
by Cas
Have you tried forward slashes?

You should create a bug ticket (milestone 1.3.x) and we can look into fixing it.