Closed kdeldycke closed 4 months ago
A vanilla mdformat is messing with Pelican curly-braces variables and replacing them with % URL escape codes:
mdformat
%
$ pipx install mdformat (...) $ mdformat --version mdformat 0.7.17 (mdformat_web: 0.1.0)
$ cat ./test.md
![My photo]({attach}photo.jpg)
$ mdformat ./test.md $ cat ./test.md
![My photo](%7Battach%7Dphoto.jpg)
That's why we have mdformat-pelican, and it works as expected:
mdformat-pelican
$ pipx inject mdformat mdformat-pelican injected package mdformat-pelican into venv mdformat done! ✨ 🌟 ✨ $ mdformat --version mdformat 0.7.17 (mdformat_pelican: 0.1.0, mdformat_web: 0.1.0)
Unformtunately, mdformat-pelican is not compatible with the addition of mdformat-gfm plugin:
mdformat-gfm
$ pipx inject mdformat mdformat-gfm injected package mdformat-gfm into venv mdformat done! ✨ 🌟 ✨ $ mdformat --version mdformat 0.7.17 (mdformat_tables: 0.4.1, mdformat_gfm: 0.3.6, mdformat_pelican: 0.1.0, mdformat_web: 0.1.0) $ mdformat ./test.md Warning: Plugin conflict. More than one plugin defined a renderer for "link" syntax.
This has also been posted at: https://github.com/gaige/mdformat-pelican/issues/3
A hackish fix has been proposed in: https://github.com/gaige/mdformat-pelican/pull/4
A hack has been merged upstream into mdformat-pelican, so I guess this issue can be closed.
A vanilla
mdformat
is messing with Pelican curly-braces variables and replacing them with%
URL escape codes:That's why we have
mdformat-pelican
, and it works as expected:Unformtunately,
mdformat-pelican
is not compatible with the addition ofmdformat-gfm
plugin:This has also been posted at: https://github.com/gaige/mdformat-pelican/issues/3