plugins/perfanno: add perfanno-nvim plugin

[FredeHoey]

Adds https://github.com/t-troebst/perfanno.nvim

perfanno-nvim was just recently added to nixpkgs, so cannot be merged until flake.lock is updated

see NixOS/nixpkgs#436798

[GaetanLepage]

I rebased on main.

[MattSturgeon]

NixOS/nixpkgs#438707 is in all unstable channels now, and should be part of the revision we've updated to.

It should be safe to remove the explicit URL now:

Suggested change

	# TODO: Remove after https://github.com/NixOS/nixpkgs/pull/438707
	url = "https://github.com/t-troebst/perfanno.nvim";

Note to self: should we throw when url is explicitly defined the same as the package's meta.homepage?

[FredeHoey]

I think that an assertion would be great. I almost feel like a build should assert if both define a url, regardless of the value, because and then assume the upstream is always correct

[FredeHoey]

@MattSturgeon I added the explicit require. Do you still think I should use literalLua for the example?

[MattSturgeon]

Testing locally with nix run .#docs:

(or without cloning: nix run github:nix-community/nixvim?ref=pull/3653/merge#docs)

Personally, I'd prefer using literalExpression or nestedLiteralLua, but this isn't a blocker.

[FredeHoey]

Oh wow, yes that looks awful 😅 I'll fix it up

…

On 10 September 2025 19.51.27 CEST, Matt Sturgeon ***@***.***> wrote: MattSturgeon left a comment (nix-community/nixvim#3653) Testing locally with `nix run .#docs`: <img width="981" height="1183" alt="image" src="https://github.com/user-attachments/assets/316beb07-fd28-4a45-ae51-34b1ac2c7bc6" /> Personally, I'd prefer using `literalExpression` or `nestedLiteralLua`, but this isn't a blocker. -- Reply to this email directly or view it on GitHub: #3653 (comment) You are receiving this because you authored the thread. Message ID: ***@***.***>

[MattSturgeon]

Sadly, using the wrong one doesn't cause a CI failure, but I believe we need nestedLiteralLua here instead of literalLua.

You may also wish to switch to using single quotes in your lua, as I don't think it is smart enough to render a '' string instead of ", unless the string includes newlines.

Or if you want full control, you can render the entire example yourself manually using a literalExpression.

You can confirm how it renders locally, using nix run .#docs (which may be a long build on the initial run).

[FredeHoey]

Fair. I did kick off the docs build, but it's still going, so I'm still waiting for the result. I'm at 7650/8389 now, so I'll wait for it to finish and validate

[MattSturgeon]

Yes, it's a shame our docs take so long. I've put effort in the past into re-implementing the docs more efficiently, but sadly none of those efforts ever made it over the line.

[FredeHoey]

@MattSturgeon take 92, how we doin? 😅

[MattSturgeon]

LGTM. Thanks for your persistence and attention to detail!