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
Is your feature request related to a problem? Please describe.
What a GREAT app !
The command $ wtsexporter -a needs to have a copy in it's working execution directory, of the "WhatsApp" Folder containing Media and Documents files. For example on Android it is located here: storage/emulated/0/Android/media/com.whatsapp/WhatsApp/
This directory might have a huge size, often several Gib.
During its execution, the above command's aim is Copying media directory... in the result folder, see command logs below:
This creates a duplicate of an already huge folder. It takes a very long time and might break the process if the destination disk runs out of free space.
Describe the solution you'd like
It might be better to have the result folder to get access to the files, media, etc... of the copied WhatsApp folder through links and not it's duplication inside result
Thus, the working execution directory, let's call it working_wts like in Usage, would need the following files or folder: wa.db WhatsApp (folder) whatsapp.cryptkey contacts.vcf (as an option, see here)
Then upon execution, the result folder would be added in working_wts. And the .html files created would get the media shared in the extracted threads through links sourced from the WhatsApp (folder).
Hence, the working execution directory, let's call it working_wts would in itself become the outcome directory (exportable, compressed into .zip or .tar.gz , etc...
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
What a GREAT app !
The command
$ wtsexporter -a
needs to have a copy in it's working execution directory, of the "WhatsApp" Folder containing Media and Documents files. For example on Android it is located here:storage/emulated/0/Android/media/com.whatsapp/WhatsApp/
This directory might have a huge size, often several Gib.
During its execution, the above command's aim is
Copying media directory...
in theresult
folder, see command logs below:This creates a duplicate of an already huge folder. It takes a very long time and might break the process if the destination disk runs out of free space.
Describe the solution you'd like
It might be better to have the
result
folder to get access to the files, media, etc... of the copied WhatsApp folder through links and not it's duplication insideresult
Thus, the working execution directory, let's call it
working_wts
like in Usage, would need the following files or folder:wa.db
WhatsApp
(folder)whatsapp.cryptkey
contacts.vcf
(as an option, see here)Then upon execution, the
result
folder would be added inworking_wts
. And the.html
files created would get the media shared in the extracted threads through links sourced from theWhatsApp
(folder).Hence, the working execution directory, let's call it
working_wts
would in itself become theoutcome
directory (exportable, compressed into .zip or .tar.gz , etc...The text was updated successfully, but these errors were encountered: