Anyway, when installing deluge-git from the AUR which is using git-develop branch(I checked), then when pressing 'p' in the console-UI, the preferences pane do show up after the initial unhandled deferred error(after second press 'p'), but only the first 3 categories work(to left) and the rest just shows blank to the right without any settings disposed. However, when installing it in a virtualenv with commands above, so using same deps as globally installed, then it works fine? That, I cannot explain or understand. The only difference is that I install slimit in the virtualenv, but it seems to be same version as the globally installed(when using deluge-git from AUR and not the stable deluge, which doesn't need slimit).
Btw, I looked through the new settings in core.conf and console.conf and hosts.conf, since I find it annoying that deluge-console non-interactive mode isn't loged in by default anymore like it used to with deluge-stable, but I found no options for enabling that. This means that every command need this e.g.:
Code: Select all
deluge-console "connect localhost ; info foo*"
Instead of just:
Code: Select all
deluge-console info foo*
This becomes extra annoying I would guess if needing to query torrents with spaces in also.
Anyway, thanks again Cas for your continued perseverance! I'm currently back on deluge myself now "fulltime" again, because I noticed that uTP support is important on public torrents with low seed-count, as many clients favor uTP which rtorrent misses + uTP supports NAT traversal for enabling access to otherwise firewalled peers. The downside to the protocol is reduced speed often compared to TCP connections, but you can set mixed-mode to prefer TCP with ltconfig plugin to mitigate this somewhat, or disable uTP completely if not caring about compatibility with "low-profile" public torrents. Also, it doesn't hurt either that deluge can be made more aggressive than other clients with it's ltconfig plugin. Sorry for momentary sidetracking there, lol