Nevertheless, I took a quick look at this plugin and looked around to see if I could help you with this problem. It looks like this plugin determines the availability of pandoc by starting a process of pandoc -v. So you should check if the pandoc executable is in your path. (try running pandoc -v from the command line and see if that works)
(I don’t have a mac so I can’t test if it works for me or if you need to do some special macos things)
Thanks for all the clarifications.
I several checked my $PATH and the command pandoc -v gave me the pandoc version.
But the pandoc is not installed tooltip is still there when I launch Inkdrop.
I still do think this is not an issue but more something from my mistake so I am not sure if I should create an issue on Github.
Hey @anon26336935,
the easiest thing to do in this case would be to start Inkdrop via a console that contains the changes to the path variable.
Otherwise you can also introduce a workaround in Inkdrop via the init.js file. (The init file - Inkdrop API Reference)
To do this, you can edit the environment variables of the process when starting Inkdrop. You can enter this in your init.js. Change the value of pandocPath to your path to the folder containing the pandoc executable. Please make sure that you use the correct separator. In my case (Linux - Ubuntu) it is the : at the beginning.
const pandocPath = ":/home/test/Desktop/pandoc-3.1.11.1-linux-amd64/pandoc-3.1.11.1/bin"
if (!process.env.PATH.includes(pandocPath)) {
process.env.PATH = process.env.PATH + pandocPath
inkdrop.notifications.addInfo("added Pandoc to the path", {dismissable: true});
}
The best solution is of course that the plugin author supports entering the path to the pandoc executable in the settings.
Thanks a lot for your help. It is really helpful to understand how things work. Well, I should read the docs first, though
I will mark your last reply as the solution since the plugin author replied to me with an update of Pandoc Inkdrop plugin : in the settings, there is an option to change the pandoc exec path and it works perfectly now!
Thanks again for your help.
I wish you a wonderful day!