--config option does not accept relative path

Hello

I have a doc repo structure like:

RepoFolderRoot
├───doc1
│       doc1.md
│       doc1.pdf
│
├───doc2
│   │   doc2.md
│   │   doc2.pdf
│
├───generate_pdf
│   │   config.json
│   │   mystyle.css

I tried to launch the md2pdf command from the root folder (for scripting) by trying: md2pdf --config-file .\generate-pdf\config.json .\doc1\doc1.md or md2pdf --config-file generate-pdf\config.json .\doc1\doc1.md or md2pdf --config-file \generate-pdf\config.json .\doc1\doc1.md

And I always got aWarning: couldn't read config file: \generate-pdf\config.json

[Zivaga]

😃 Sure. I will use it in a more scripted way very soon. If I think about ant improvement, I’ll let you know.

Thanks!

[nekloth]

Hi

The relative path changed… it used to consider the relative path from the execution path, now, it considers relative path from the MD file.

It used to work with:

  "stylesheet": [
    ".\\mystyle.css"
  ],

when executed from c:\RepoFolderRoot\

Error is:

 md2pdf --config-file .\generate_pdf\config.json ./doc1/doc1.md
  × generating PDF from ./doc1/doc1.md
    → ENOENT: no such file or directory, open 'c:\RepoFolderRoot\doc1\mystyle.css'

and now works with…

  "stylesheet": [
    "C:\\RepoFolderRoot\\generate_pdf\\mystyle.css"
  ],

It is not very convenient for me, as my stylesheet lifecyle is different from doc lifecycle, and I’m not the only one to use this repo (and of course, all of us do not have the same folder organisation…)