Hello, thanks for your help. ... you seem to be bugged. You posted seven
messages that look about the same, all this after my question:

||litlighilit
APP
 — 17:30
c code is always generated.All you need is to add --nimcache flag to specify
where the c code to put in
----------
-c works, it means stopping after C code is generated, without calling C
compiler to compile.
Hi, maybe too late to ask but it's surely what I wondered the day before
yesterday:
How did you guys deploy nim doc in github, if using CI to be automated?
I've made and published nimpylib/doc-deploy action ready to uses at
https://github.com/marketplace/actions/nimdoc-deploy,And detailed info is
described at forum:
https://forum.nim-lang.org/t/13580#82376Or join #nimpylib-actions\:envs.net room
if neither is unavailable for you
Hi, maybe too late to ask but it's surely what I wondered the day before
yesterday:
How did you guys deploy nim doc in github, if using CI to be automated?
I've made and published nimpylib/doc-deploy action ready to uses at
https://github.com/marketplace/actions/nimdoc-deploy,And detailed info is
described at forum:
https://forum.nim-lang.org/t/13580#82376Or join #nimpylib-doc-deploy\:envs.net
room if neither is unavailable for you
Edit: c code is always generated, in nimcache directory (often under your HOME
directory)All you need is to add --nimcache flag to specify where the c code to
put in
----------
-c works, it means stopping after C code is generated, without calling C
compiler to compile.||