-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
split_pdf on Windows PC #14
Comments
Probably related to slash directions on the filepath |
Yeah, stupid me 🤦♂️ |
no no. it's our fault if R/unix style slashes break things on windows. I just wrote it as the potential issue to return for a fix later |
About it hanging itself, does it happen on the mac? See #7 if it does. About the slash issue, were you actually able to fix it by changing slash directions? Because I can't replicate the issue on my windows |
The infinite loop only occurred on Windows so far. Regarding the solution: I used the file.path() function on it so it autocorrected on any OS. My misconception was due to lacking documentation. I’d suggest to describe to attribute types more precisely. For this take reference to Hadley Wickhams book on R packages http://r-pkgs.had.co.nz/man.html#man-functions |
Could you give me the path that failed. Because based on my experimentation in windows, it works with any combination of I tried to replicate your code by making some assumptions about your file structure. I placed a pdf at the path Based on this structure your code doesn't and shouldn't work regardless of the OS as it is trying to place the output at If I understand what went wrong to begin with I can see if some explanation could be added to the docs |
I have an issue migrating my code from MacOS to Windows devices.
The following code snippet works just fine on my MacOS but hangs itself after the first iteration:
I installed pdftk on both devices and they work fine, so I guess it's an issue regarding staplr.
Any suggestions to quickly solve the issue?
The text was updated successfully, but these errors were encountered: