Leadbelly

Thanks for checking out my issue 😊 Unfortunately it seems the issue persists on your branch. Just to double check I'm running the patch correctly - this is how I...

I've reverted the cahnge to the LazyVim checkout (now checked out at v14.14.0 again). I've also added the file you suggested (although, this is a different thing to the above...

Yes, I've got dap.core extra installed. ```lua require("lazy").setup({ spec = { { "LazyVim/LazyVim", import = "lazyvim.plugins" }, { import = "lazyvim.plugins.extras.dap.core" }, { import = "lazyvim.plugins.extras.lang.rust" }, }, }) ```...

Aha! Yes that's it. I've got a vscode config file hanging around which is interfering with the LazyVim config. Thanks! Good shout . I'm unblocked 🙏🏻 This does seem like...

Yep, it was the presence of the vs code config (.vscode/launch.json) which caused the wrong adapter to be configured. I do think that this is a bug on the nvim...

My instinct is that nvim / vscode interop should be an opt-in feature. But anyway, as you say, this is not the place for that discussion. I'll open up a...

Thanks for the PR! 🏅

This patch would have cargo semver checks running on each PR against develop. This would be redundant since the check only makes sense to run on **releases** - PRs against...

BTW, I'm currently working on some automatic release [start](https://github.com/BenLeadbetter/bl-midi2-rs/blob/develop/.github/workflows/start-release.yml) / [finish](https://github.com/BenLeadbetter/bl-midi2-rs/blob/develop/.github/workflows/finish-release.yml) actions which would also automatically run the checks, but these are still WIP.

Hello! > How would one use this trait for an application that might create multiple messages triggered by an event? TLDR: `UmpMessage` is a pretty good choice. Which trait are...