Closed HannoSpreeuw closed 2 months ago
I have the same issue, running Entangled 2.0.3. The error only occurs on code blocks with a block identifier. However there is no problem when the filename is already used in another block without blockid.
This causes an error
``` {.rust #blockid file=world.rust}
...
but this works
...
and this also works
...
some text
...
These are two unrelated issues. @HannoSpreeuw: this happens when you're running entangled when there is a filedb
from an older version. This is still an issue, but not a very pressing one.
Make sure that there are no dangling changes in the tangled source files before running:
rm .entangled/filedb.json
entangled tangle --force
Still, entangled shouldn't crash this ugly when the filedb
is damaged.
@RaFortunat Thanks. I created a new issue for this.
I'm completely mistaken: this is the same issue. But it is fixed now. Closing
This is Entangled 2.0.2. Running
entangled watch
from a conda py311 env in a Julia repo. This gives