How? Transmission Remote GUI path for containing folder

eton wrote:
nasischijf wrote: The following has been working for me: /data/Transmission/Downloads/=afp:\\HostnameOfMyNAS\Transmission\Downloads\ Wow, interesting. Backslashes on OS X? Looks crazy. Does it really work for you on OS X? Or do you run OS X virtually or something like that? It did not work for me (I tried with both server name and IP number).

I don't know how I came up with it, but it works on Mountain Lion and (as I've checked just now) on Mavericks.
Note: AFP should be enabled for the folder.

eton wrote:

OMG! I solved it with your help. The server path is NOT the full local path, just the "mapped" path as the server sees it (I don't know how to express it better). This worked for me! /media/BitTorrent/=afp:\\[server name or IP]\media\BitTorrent\ With that knowledge, the mapped drive method also works and it's faster: /media/BitTorrent=/Volumes/media/BitTorrent Note that the "Open containing folder" function only works with fully downloaded files (or with other words not for files stored in the incomplete folder). Also note that Transmission Remote GUI doesn't care if you use forward or backward slashes. The local path on the server is as (as you know) /c/media/BitTorrent/ but to make it work with Transmission Remote GUI you will have to modify it to what is shown over the network, in this case: /media/BitTorrent/. Messy

I think the code from my previous message is a safer bet, because you're line of code uses a mapped folder on the server (i.e. /media/BitTorrent). I've just checked, and it appears it's not a default map/mount. I've ssh'ed to my ReadyNas, no mount points in /media, but Transmission seems to use /data/Transmission anyway by default.

If you've opened a folder from Transmission Remote GUI once, the next one will be faster because you probably stay connected.

Glad it worked for you Eton!