KillTheMule
KillTheMule
> That logic seems sound to me. I tried to run the example and I've seen it just work as expected. yet when I run something like > > ```rust...
>Can be triggered by just doing this with a relatively recent version of Neovim: >echo -e -n '\x94\x00\x0a' | ./build/bin/nvim --embed Even that did not reproduce on latest neovim master,...
Ok, so with current neovim HEAD (8df3742), I can reproduce that, both on my PC and my thinkpad. When running the rust code, the last buffer name change I can...
@strottos In the neovim issue, you wrote > I've tracked it down to that Rust sometimes will send just this bytes snippet: How did you track that down? I can...
I did investigate some, I've added my findings to the neovim issue.
I've written some details in the neovim issue, but overall the line buffering from rust's stdout is triggering the issue, so I'll work on removing that.
Anyone interested in trying out https://github.com/KillTheMule/nvim-rs/pull/48? This should fix the issue from `nvim-rs`'s side, although I'll be looking into fixing it in neovim later on.
Closed by https://github.com/KillTheMule/nvim-rs/pull/48, will cut a new release.
I assume there already are plugins for that, did you have a look? E.g https://github.com/tpope/vim-projectionist
This isn't what you're asking for, but when putting external data into typst documents I'd suggest you either use [`sys.inputs`](https://docs.rs/typst/latest/typst/struct.LibraryBuilder.html#method.with_inputs), if you're using typst as a library, or its [`data...