consecutive (or custom) image filenames #204
Comments
|
Sure, that is maybe better anyway. The idea with the hash was that you would have some connection between the code that generated the file, but not sure that is so useful. |
|
If you run multiple Literate files in the same directory you would get name-clashes though, which the current approach minimizes I guess. Documenter just uses a random number, but not sure that is much better than the current hash method. |
|
Yes, I would prefer the clashing filenames to be silently overwritten. I would not recommend this as the default though. |
|
The names could perhaps be |
|
Yes, that would be perfect for my purposes. |
fredrikekre
added a commit
that referenced
this issue
Sep 22, 2022
When executing markdown (Literate.markdown(...; execute=true) images
where previously saved to files where the name was based on the hash of
the source block. This patch changes this such that files instead follow
the format {name}-{blocknumber}.(svg|png|...). Closes #204.
fredrikekre
added a commit
that referenced
this issue
Sep 22, 2022
When executing markdown (Literate.markdown(...; execute=true) images
where previously saved to files where the name was based on the hash of
the source block. This patch changes this such that files instead follow
the format {name}-{blocknumber}.(svg|png|...). Closes #204.
|
Fixed in #205, released in 2.14.0 (JuliaRegistries/General#68765). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently image filenames are calculated using a hash. This is useful, but when working on a document incrementally, the directory gets cluttered with a bunch of files that are no longer used.
Would it make sense to have an option to consecutively generates filenames with a counter? Eg
1.svg,2.svg, etc.The text was updated successfully, but these errors were encountered: