-
Notifications
You must be signed in to change notification settings - Fork 6k
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
[Bug] Download file (.md/.pdf) is working, but the 'open_file' command fails #242
Comments
Please try v0.10.0 |
Just tried it - the correct folder now opens, but the file does not;
Should the open_file command open the file in a default application? Also, the pdf looks like it's one long image pasted into a pdf. Is that the intended behaviour? |
It will only open the directory where the file is located, not open the file (this is the expected behavior, because considering the exported file may require secondary operations by the user, so did not open the file itself). PDF export using jsPDF, I have not yet studied in depth whether its API supports text content. |
When you're handling the pdf it looks like you're putting a .png image in there from the code:
Maybe you can inject the .md file instead of a png. I'm just guessing here. |
If you just inject markdown you will lose the style, it should be html with css. |
Am I misreading the code above that's injecting imgData, PNG? |
The code snippet you sent is the code that generates the PDF, which is drawn via canvas, and I also found a related issues to explain how it works now. parallax/jsPDF#1580 (comment) |
Version
v0.9.2
Bug description
I think the issue here, on Windows machines, in the open_file command, the path argument contains a mix of forward and back slashes. The Open_file command then just opens an Explorer window to a default path, and not the file just downloaded.
Example, from my log file I see:
open_file: C:\Users\MXX.chatgpt\download/pdf/fq2fbm.pdf
I think this fails because of the forward slashes - this is my guess.
OS
Windows 10
Environment
No response
The text was updated successfully, but these errors were encountered: