fix: use non-NUL separator in mermaid_cache_path#8
Merged
Conversation
The NUL byte separator in mermaid_cache_path causes the Lua→vimscript bridge to convert the concatenated string to a Blob on Neovim ≤ 0.11, which vim.fn.sha256 rejects with E976. Using '|' avoids the Blob conversion entirely. Fixed upstream in v0.12 (vim-patch 9.1.1774).
hambergerpls
force-pushed
the
fix/sha256-blob-error
branch
from
1875631 to
18aefde
Compare
hambergerpls
changed the title
delphinus
approved these changes
Apr 29, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
"\0") for"|"inmermaid_cache_pathvim.fn.sha256()rejects with E976Closes #7