Closed dagerber closed 8 years ago
Thanks for catching this!
Looks like this appeared in 0.2.2, with the Python 3 compatibility code being the likely culprit. I shouldn't have tested it with just the -o
option (which worked fine). For now you can use one of the following two workarounds:
file
using the -o
option: mkdocs2pandoc -o file
(this will work for 0.2.2 as well)Works like a charm. Thanks for your valuable work!
I'm glad the workaround works for you, but I'll leave this open nonetheless if you don't mind, since I'd rather fix this for all use cases including the one that didn't work for you :-)
Fixed in https://github.com/jgrassler/mkdocs-pandoc/commit/abe0f268187da76958d804e3f9fd066d496b426c. This is the basis for the new release 0.2.3.
mkdocs2pandoc gives no output an no error message.
Would be great, if you could add some logging, possibly a '-v' switch
No output...