debug log belongs in cache directory not config directory (#179)

* log files are now written to cache dir instead of config dir

* lint

* fmt

docs/de/man.md

@@ -482,9 +482,9 @@ Just a reminder: **you can edit only textual file**; binary files are not suppor
 
 termscp writes a log file for each session, which is written at
 
-- `$HOME/.config/termscp/termscp.log` on Linux/BSD
-- `$HOME/Library/Application Support/termscp/termscp.log` on MacOs
-- `FOLDERID_RoamingAppData\termscp\termscp.log` on Windows
+- `$HOME/.cache/termscp/termscp.log` on Linux/BSD
+- `$HOME/Library/Caches/termscp/termscp.log` on MacOs
+- `FOLDERID_LocalAppData\termscp\termscp.log` on Windows
 
 the log won't be rotated, but will just be truncated after each launch of termscp, so if you want to report an issue and you want to attach your log file, keep in mind to save the log file in a safe place before using termscp again.
 The logging by default reports in *INFO* level, so it is not very verbose.

docs/es/man.md

@@ -481,9 +481,9 @@ En caso de que el archivo esté ubicado en un host remoto, el archivo se descarg
 
 termscp escribe un archivo de registro para cada sesión, que se escribe en
 
-- `$HOME/.config/termscp/termscp.log` en Linux/BSD
-- `$HOME/Library/Application Support/termscp/termscp.log` en MacOs
-- `FOLDERID_RoamingAppData\termscp\termscp.log` en Windows
+- `$HOME/.cache/termscp/termscp.log` en Linux/BSD
+- `$HOME/Library/Caches/termscp/termscp.log` en MacOs
+- `FOLDERID_LocalAppData\termscp\termscp.log` en Windows
 
 el registro no se rotará, sino que se truncará después de cada lanzamiento de termscp, por lo que si desea informar un problema y desea adjuntar su archivo de registro, recuerde guardar el archivo de registro en un lugar seguro antes de usar termscp de nuevo.
 El registro por defecto informa en el nivel *INFO*, por lo que no es muy detallado.

docs/fr/man.md

@@ -479,9 +479,9 @@ Si le fichier se trouve sur l'hôte distant, le fichier sera d'abord télécharg
 
 termscp écrit un fichier journal pour chaque session, qui est écrit à
 
-- `$HOME/.config/termscp/termscp.log` sous Linux/BSD
-- `$HOME/Library/Application Support/termscp/termscp.log` sous MacOs
-- `FOLDERID_RoamingAppData\termscp\termscp.log` sous Windows
+- `$HOME/.cache/termscp/termscp.log` sous Linux/BSD
+- `$HOME/Library/Caches/termscp/termscp.log` sous MacOs
+- `FOLDERID_LocalAppData\termscp\termscp.log` sous Windows
 
 le journal ne sera pas tourné, mais sera simplement tronqué après chaque lancement de termscp, donc si vous souhaitez signaler un problème et que vous souhaitez joindre votre fichier journal, n'oubliez pas de sauvegarder le fichier journal dans un endroit sûr avant de l'utiliser termescp à nouveau.
 

docs/it/man.md

@@ -478,9 +478,9 @@ Nel caso il file si trovi su host remoto, il file verrà prima scaricato tempora
 
 termscp scrive un file di log per ogni sessione, nel percorso seguente:
 
-- `$HOME/.config/termscp/termscp.log` su Linux/BSD
-- `$HOME/Library/Application Support/termscp/termscp.log` su MacOs
-- `FOLDERID_RoamingAppData\termscp\termscp.log` su Windows
+- `$HOME/.cache/termscp/termscp.log` su Linux/BSD
+- `$HOME/Library/Caches/termscp/termscp.log` su MacOs
+- `FOLDERID_LocalAppData\termscp\termscp.log` su Windows
 
 Il log non viene ruotato, ma viene troncato ad ogni lancio di termscp, quindi se devi riportare un issue, non avviare termscp fino a che non avrai salvato il file di log.
 I log sono di default riportati a livello *INFO*, quindi non sono particolarmente parlanti.

docs/man.md

@@ -480,9 +480,9 @@ In case the file is located on remote host, the file will be first downloaded in
 
 termscp writes a log file for each session, which is written at
 
-- `$HOME/.config/termscp/termscp.log` on Linux/BSD
-- `$HOME/Library/Application Support/termscp/termscp.log` on MacOs
-- `FOLDERID_RoamingAppData\termscp\termscp.log` on Windows
+- `$HOME/.cache/termscp/termscp.log` on Linux/BSD
+- `$HOME/Library/Caches/termscp/termscp.log` on MacOs
+- `FOLDERID_LocalAppData\termscp\termscp.log` on Windows
 
 the log won't be rotated, but will just be truncated after each launch of termscp, so if you want to report an issue and you want to attach your log file, keep in mind to save the log file in a safe place before using termscp again.
 The logging by default reports in *INFO* level, so it is not very verbose.

docs/zh-CN/man.md

@@ -472,9 +472,9 @@ Termscp有很多功能，你可能已经注意到了，其中之一就是可以
 
 termscp会为每个会话创建一个日志文件，该文件在
 
-- `$HOME/.config/termscp/termscp.log` -- Linux/BSD
-- `$HOME/Library/Application Support/termscp/termscp.log` -- MacOs
-- `FOLDERID_RoamingAppData\termscp\termscp.log` -- Windows
+- `$HOME/.cache/termscp/termscp.log` -- Linux/BSD
+- `$HOME/Library/Caches/termscp/termscp.log` -- MacOs
+- `FOLDERID_LocalAppData\termscp\termscp.log` -- Windows
 
 日志不会被轮换，但只会在每次启动 termcp 后被截断，因此如果您想报告问题并希望附加您的日志文件，请记住在使用前将日志文件保存在安全的地方 再次termscp。
 默认情况下，日志记录在 *INFO* 级别报告，因此它不是很详细。