Uncaught Error: ENOENT, open 'c:\devel\tools\cpdfer\Readme.md' about markdown-pdf HOT 9 CLOSED

From @50Wliu on February 4, 2015 15:2

/cc @benogle

from markdown-pdf.

I assume this is a issue with markdown-pdf.

from markdown-pdf.

Maybe some dir on the c:\devel\tools\cpdfer\ path doesnt exist?

from markdown-pdf.

@baskinomics

Do you still get this issue?

I am not quite sure what's going on here

from markdown-pdf.

@hdmi @baskinomics

Hey there, I'm still trying to reproduce this issue and cannot. Is the .md file saved before you attempt to convert it?
Also, it is informative that this occurs on different operating systems. Is there any more information you thin may be pertinent to resolving this?

Thanks for the reports! 🐛

from markdown-pdf.

I've done some tests (in linux) and here are the outputs:

Open atom from terminal with normal rights (no sudo):

• Create a new document, write some markdown and save it as Document1.md
  • Output: ENOENT...
• Create a new document, write some markdown and save it as Document2.markdown
  • Output: It generates the file correctly

I have renamed my files ending with .md to .markdown and all the problems with the pdf conversion disappeared.

from markdown-pdf.

Sorry I haven't been contributing to this, haven't really been using Atom in the day-to-day workplace (yet ;). I can't remember exactly what I was attempting to do, but I can confirm that the path c:\devel\tools\cpdfer\ does not exist on my machine.

from markdown-pdf.

@travs

I've gotten this issue and I think I know the problem. The directory is probably supposed to be c:\devel\tools\cmder\, but it's replacing "md" at the wrong spot, leading to "cpdfer".

I have the same problem. My username is "adamdrago" and I get this error:

Uncaught Error: ENOENT: no such file or directory, open '/Users/adapdfrago/Desktop/Notes/geo-pd/GEO-PD.md'

Notice how "adamdrago" betcomes "adapdfrago"?

Hopefully this helps solve the problem!!

from markdown-pdf.

Thanks @atdrago for your help, now I realize where the problem comes from.
As you said, the package was replacing in the path a substring composed by 'md' to 'pdf'.

I have modified the function which returns the path of the new pdf file, and it seems to work perfectly.
You can see the modifications in the commit d0c1faf

from markdown-pdf.