-
Notifications
You must be signed in to change notification settings - Fork 30
repush: uppercase extension PDF does not work #21
Comments
Perl regexes are not needed here, so I just removed the |
Thanks, this renders my edits unnecessary, I can push .pdf files now. for what it's worth I still can't push .PDF files: I try to push schematiccap.PDF and I get a blank file on the remarkable called schematiccap.pdf (it appears, it has a cloud-download icon, then it gets a checkmark - so I assume it finishes). But the repush.sh script never finishes, I eventually ctrl-C to exit it.
|
I just tried again with 1.7. The name on my device has an uppercase suffix (-> ".PDF"). Maybe 2.0 changes suffixes to lower case. If that's the case, the script wouldn't be able to leave the loop in line 362. I don't have 2.0, so all I can do is guess, unfortunately. You could try changing the suffix of the name that is used internally to lowercase. That way, even if the web interface changes the case of the file name, repush won't get stuck. If that actually solves the problem, I will write a more general version and submit yet another PR. |
I said this elsewhere, but thank you for this script.
I have it working to send pdf files from my mac to my tablet, and I'm very happy about that.
I can't send epub files, per #14 (which is fine with me)
Also, I can only send files that are .pdf, not .PDF.
if I send a .PDF file, a blank pdf is created in the root directory on reMarkable with the lower-case filename, and the script seems caught in an infinite loop.
Likely this should be caught by the error-catching code that I removed on my machine since my grep does not have -P
The first thing I tried was naively rewriting the above to only check for "pdf" (since I disabled the epub issue to get up and running on a mac with no -P option in grep)
The result of this is somewhat interesting: when I send a file like filename.PDF,
The text was updated successfully, but these errors were encountered: