utility/preview/live-preview: init

[rv178]

Add support for live-preview.nvim, a live preview plugin to preview markdown, HTML, AsciiDoc and SVG files in a web browser with live updates.

Additional note: Since nixpkgs packages the latest tagged release (v0.9.6), it calls a vim.uv.run() from inside nvim's active event loop, causing the editor to freeze when the server starts. I'm directly doing a fetchFromGitHub() to pin the version to the latest commit as that applies the fix. However, I did not see this being done in any other plugins, so I would love to know the correct approach here :)
Using npins now.

Sanity Checking

• I have updated the changelog as per my changes
• I have tested, and self-reviewed my code
• My changes fit guidelines found in hacking nvf
• Style and consistency
  • I ran Alejandra to format my code (nix fmt)
  • My code conforms to the editorconfig configuration of the project
  • My changes are consistent with the rest of the codebase
• If new changes are particularly complex:
  • My code includes comments in particularly complex areas
  • I have added a section in the manual
  • (For breaking changes) I have included a migration guide
• Package(s) built:
  • .#nix (default package)
  • .#maximal
  • .#docs-html (manual, must build)
  • .#docs-linkcheck (optional, please build if adding links)
• Tested on platform(s)
  • x86_64-linux
  • aarch64-linux
  • x86_64-darwin
  • aarch64-darwin

---

Add a 👍 reaction to pull requests you find important.

[github-actions]

🚀 Live preview deployed from f019fe8

View it here:

Debug Information

Triggered by: rv178

HEAD at: main

Reruns: 4033

[alfarelcynthesis]

You should probably add the plugin using npins instead, like with most other plugins. This would still allow you to set it directly to a commit (using --at ref).

nvf generally avoids using nixpkgs-packaged vim plugins afaik, for reasons like this one.

[alfarelcynthesis]

More info: https://github.com/NotAShelf/nvf/blob/main/docs/manual/hacking.md#with-npins-sec-npins-for-plugins