You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On GNU/Linux: We will be using $XDG_CONFIG_HOME/gtorrent which usually translates to ~/.config/gtorrent
This is the working directory of gTorrent, it's where it will store:
Session data
Config data
On Windows:We will use %APPDATA%\gtorrent -- No, let's not forget how retarded some Windows babbies can get. Some anon suggests %APPDATA%\gtorrent for session related data and the user's home directory for configuration files. I +1 that.
On Mac: See GNU/Linux.
Obviously the fact that we'll have to split up where user configs and session data is stored makes this irritating as we can't use the same DIR. Therefore, on all core systems, there'll be two MACROs used to define where config/session data is stored, even if it is the same on GNU/Linux and Mac.
The text was updated successfully, but these errors were encountered:
Issue by nyanpasu
Thursday Jul 17, 2014 at 16:34 GMT
Originally opened as https://github.com/gtorrent/gTorrent-legacy/issues/77
We have a partial implementation of this.
On GNU/Linux: We will be using
$XDG_CONFIG_HOME/gtorrent
which usually translates to~/.config/gtorrent
This is the working directory of gTorrent, it's where it will store:
On Windows:
We will use-- No, let's not forget how retarded some Windows babbies can get. Some anon suggests%APPDATA%\gtorrent
%APPDATA%\gtorrent
for session related data and the user's home directory for configuration files. I +1 that.On Mac: See GNU/Linux.
Obviously the fact that we'll have to split up where user configs and session data is stored makes this irritating as we can't use the same DIR. Therefore, on all core systems, there'll be two MACROs used to define where config/session data is stored, even if it is the same on GNU/Linux and Mac.
The text was updated successfully, but these errors were encountered: