Custom Query (2447 matches)

Deluge uses the Python "logging" module for warnings, errors, and debugging statements. By default, the logging module outputs everything to stderr (or stdout?). But this does not work with deluge-console, because it is using ncurses. Anything written to stdout or stderr will not print out correctly when using a program written in ncurses.

(All the debugging statements do work correctly when using deluge-console and logging to a file instead of the terminal.)

I've come up with a couple different solutions to this.

1. Error out when the user tries to run deluge-console with a log level above "none" and does not specify a logfile.

2. Buffer all the logging output and print it to the console right before deluge-console closes. (After stdscr.endwin() is called.)

3. Write a wrapper around the LOG object (from deluge.log) that creates an event every time something is output to the log. Then deluge-console can catch this event and print the log message just like its own output (within its own terminal). The only downside of this is that there could be no use of log.error() or log.debug() or similar functions within the functions that print to the terminal in deluge-console. This includes ConsoleUI.write() and Screen.addline().

I would be willing to work on implementing any of these, but I don't want to start work on something that definitely won't be accepted.

In deluge-gtk, in Connection Manager, there is no way to modify an existing connection profile. Annoying when you typed a wrong password.

I noticed that extracting does not always work properly. This happens when the downloaded (for example) .rar files have spaces in them. The files to be extracted should get " (or get escaped of course) along with them.

So:

unrar -x "totally legal thing I downloaded.rar"
or
unrar -x totally\ legal\ thing\ I\ downloaded.rar
in stead of
unrar x totally legal thing I downloaded.rar

Also note that I have my "Extracted directory" in my "completed directory"

So my relevant tree looks like so:

deluge/downloading
deluge/completed
deluge/completed/extracted

(maybe that's got something to do with it? Haven't looked at the code, so I wouldn't know)

The unrar command under Linux doesn't like it that way. (it'll only see the "totally" part of the file) I'm using 1.2.0 beta5, but earlier beta's had the same thing.