plugins/timerly: init

[FKouhai]

No description provided.

[FKouhai]

I tried the plugin locally with an updated flake

[GaetanLepage]

You are on a good start. Few comments.

[MattSturgeon]

I'm glad to see only the tests related to this plugin and the docs are failing though, meaning we've managed to achieve the lazy evaluation of packages described in #2004 🎉

i.e. if your nixvim doesn't use a particular plugin/package, the nixvim eval doesn't depend on it existing in your nixpkgs revision.

[MattSturgeon]

No issues from me, but is blocked by us bumping to a newer nixpkgs revision. See #3318

[MattSturgeon]

should I nix flake update? the package is already in nixpkgs unstable

No, we'll handle the bump in #3318. You'll just have to rebase once that's merged.

Merged, should be good to rebase now

[FKouhai]

should I nix flake update? the package is already in nixpkgs unstable

No, we'll handle the bump in #3318. You'll just have to rebase once that's merged.

Merged, should be good to rebase now

omw boss

[mergify]

This pull request, with head sha 1c53ad9b2f5fd4a3c1f644d03895cda7756c92a3, has been successfully merged with fast-forward by Mergify.

This pull request will be automatically closed by GitHub.

As soon as GitHub detects that the sha 1c53ad9b2f5fd4a3c1f644d03895cda7756c92a3 is part of the main branch, it will mark this pull request as merged.

It is possible for this pull request to remain open if this detection does not happen, this usually happens when a force-push is done on this branch feat/add_timerly, this means GitHub will fail to detect the merge.

[MattSturgeon]

Thanks!

[GaetanLepage]

Well done @FKouhai!