Skip to content
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

Error on export return code: 43 #886

Closed
josecupchik opened this issue Jun 8, 2021 · 7 comments
Closed

Error on export return code: 43 #886

josecupchik opened this issue Jun 8, 2021 · 7 comments
Labels
Milestone

Comments

@josecupchik
Copy link

I get this message during preview for PDF but this export the file, but no all the time.
Screenshot from 2021-06-08 12-06-17

@TheJackiMonster
Copy link
Collaborator

Yes, I also experienced this. The problem about fixing this is that we had a quite similar problem because this happens basically everytime Pandoc changes its parameters or specs. So I would actually like to see a fix for this which prevents it to happen again in the future but I'm not sure if that is possible.

@obw
Copy link
Contributor

obw commented Jun 8, 2021

What about a INI file with the parameters for pandoc?

When we use sections, we can also support multiple Versions of pandoc.

Could be something like that:

[pandoc.ver 1.19.2.4]
toc-depth={{toc-depth}}
--standalone=__NONE__
...

[pandoc.ver 1.19.2.5]
...

If __NONE__, then no parameter.
If in two curly braces, then var replacement and a parameter with value.
Everything else parameter, which should use the given value.

When there is a new pandoc version, which makes trouble, only the ini must be corrected, in a step later, we could make something like an updater only for this file. Should be easy. So no coding is needed and when someone is forced to use an older version of pnadoc, it's also working, because the parameter collection, is avail in the ini.

Regards

P.S.: We could also use wildcards to group versions (something like [pandoc.ver 1.19.2.*] for all 1.19.2 versions) and defaults with this System, but it will make more work to implement.

@TheJackiMonster
Copy link
Collaborator

What about a INI file with the parameters for pandoc?

Yes, that sounds like a good solution. So we good properly inform the user about a Pandoc version mismatch if a newer configuration on out side is missing. We should definitely not hardcore this as before every time Pandoc changes and becomes incompatible with Manuskript.

@josecupchik
Copy link
Author

If I understand correctly, I have to install an older version of Pandoc.
How can I do it?

@TheJackiMonster
Copy link
Collaborator

Technically there are all releases as downloads on Pandocs Github repository: https://github.com/jgm/pandoc/releases

But I'm not sure currently which is the last compatible version.

@josecupchik
Copy link
Author

josecupchik commented Jun 10, 2021 via email

@TheJackiMonster
Copy link
Collaborator

As mentioned in issue #922 I have now implemented a change to pick options for Pandoc depending on the version of the installed binary. So this issue should be solved with future releases without any user going to the Pandoc release page manually.

@TheJackiMonster TheJackiMonster added this to the 0.13.0 milestone Nov 27, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants