tools:cooklang
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | |||
| tools:cooklang [2026/08/24 16:33] – [Updating cookcli] Julien Deswaef | tools:cooklang [2026/08/24 16:34] (current) – [Dokuwuki plugin] Julien Deswaef | ||
|---|---|---|---|
| Line 5: | Line 5: | ||
| I’ve started writing some [[recipes: | I’ve started writing some [[recipes: | ||
| - | - I needed to figure out how to install | + | - I needed to figure out how to install |
| - After that, I had to figure out how to configure the Dokuwiki to actually find it. It’s all about finding the right path. | - After that, I had to figure out how to configure the Dokuwiki to actually find it. It’s all about finding the right path. | ||
| - But even after that the plugin would still return an error and never display properly a recipe. | - But even after that the plugin would still return an error and never display properly a recipe. | ||
| - | - Turns out at OVH compiles its PHP with `--enable-sigchild` which makes `proc_close`, a function that the plugin calls to close the connection with `cook` always return undefined or an error. So the plugin never moves to displaying the recipe. | + | - Turns out at OVH compiles its PHP with '' |
| - After chatting with Gemini for a while to debug this PHP issue and look for alternative. Gemini suggested to create a third output pipeline just to catch the return of the command. That seemed to have done the trick. The forked and working code is here https:// | - After chatting with Gemini for a while to debug this PHP issue and look for alternative. Gemini suggested to create a third output pipeline just to catch the return of the command. That seemed to have done the trick. The forked and working code is here https:// | ||
tools/cooklang.txt · Last modified: by Julien Deswaef
