fujin/rtorrent
1
0
Fork 0
mirror of https://github.com/rakshasa/rtorrent.git synced 2026-10-11 16:49:22 +00:00
Code Issues Packages Projects Releases Wiki Activity

Updated Common Tasks in rTorrent (rest)

PyroScope Project
2017-08-03 20:51:54 +02:00
parent 878a194ef8
commit fec2fe60fa
1 changed files with 3 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
Common-Tasks-in-rTorrent.rest
+3 -1
@@ -61,7 +61,7 @@ Create symbolic links to indicate the download state
Move completed torrents Move completed torrents
------------ ------------
**This is just broken, read [#625](/rakshasa/rtorrent/issues/625).** **This is just broken, read** `#625 </rakshasa/rtorrent/issues/625>`_.
When the torrent finishes, it executes ``mv <base_path> ~/Download/`` and then sets the destination directory to ``~/Download/`` (using the above defined ``d.get_data_full_path`` method). When the torrent finishes, it executes ``mv <base_path> ~/Download/`` and then sets the destination directory to ``~/Download/`` (using the above defined ``d.get_data_full_path`` method).
@@ -75,6 +75,8 @@ When the torrent finishes, it executes ``mv <base_path> ~/Download/`` and then s
Move completed torrents to different directory depending on watch directory Move completed torrents to different directory depending on watch directory
------------ ------------
**This is just broken, read** `#625 </rakshasa/rtorrent/issues/625>`_.
Each watch directory adds torrents with the final destination stored in the ``custom1`` string of the download. You can check this string with ``^x`` then ``print=$d.custom1=`` in the client (using the above defined ``d.get_data_full_path`` method). Each watch directory adds torrents with the final destination stored in the ``custom1`` string of the download. You can check this string with ``^x`` then ``print=$d.custom1=`` in the client (using the above defined ``d.get_data_full_path`` method).
.. code-block:: .. code-block::