@GrahamcOfBorg build vimPlugins.unisonSyntax

The manual on vim says you should add a new plugin like this

• https://github.com/NixOS/nixpkgs/blob/master/doc/languages-frameworks/vim.section.md#adding-new-plugins-to-nixpkgs

The manual on vim says you should add a new plugin like this

• https://github.com/NixOS/nixpkgs/blob/master/doc/languages-frameworks/vim.section.md#adding-new-plugins-to-nixpkgs

OK, i'll read that and see if it's applicable here.
Sorry for the delay, i completely forgot i'd created this PR :)

The manual on vim says you should add a new plugin like this

• https://github.com/NixOS/nixpkgs/blob/master/doc/languages-frameworks/vim.section.md#adding-new-plugins-to-nixpkgs

OK, i'll read that and see if it's applicable here.
Sorry for the delay, i completely forgot i'd created this PR :)

Ah I remember why i did it this way!

I wanted the nix package name to be different than the git repo name, since the repo isn't holding just a vim plugin, but rather the "plugin" (really, just syntax-related files) is a small bit inside the repo.

The manual on vim says you should add a new plugin like this

• https://github.com/NixOS/nixpkgs/blob/master/doc/languages-frameworks/vim.section.md#adding-new-plugins-to-nixpkgs

OK, i'll read that and see if it's applicable here.
Sorry for the delay, i completely forgot i'd created this PR :)

Ah I remember why i did it this way!

I wanted the nix package name to be different than the git repo name, since the repo isn't holding just a vim plugin, but rather the "plugin" (really, just syntax-related files) is a small bit inside the repo.

...also, the fetch doesn't need the repo submodules, for instance.

The manual on vim says you should add a new plugin like this

• https://github.com/NixOS/nixpkgs/blob/master/doc/languages-frameworks/vim.section.md#adding-new-plugins-to-nixpkgs

OK, i'll read that and see if it's applicable here.
Sorry for the delay, i completely forgot i'd created this PR :)

Ah I remember why i did it this way!
I wanted the nix package name to be different than the git repo name, since the repo isn't holding just a vim plugin, but rather the "plugin" (really, just syntax-related files) is a small bit inside the repo.

...also, the fetch doesn't need the repo submodules, for instance.

...oh yeah, and it's meant to be pinned to particular repo versions.
Given all of this, @worldofpeace let me know if you still want me to follow those instructions. The end result will probably look very similar, since all the relevant data (git sha, overriding submodule fetch, preInstall step, etc) will all still be present in overrides.nix.

Let me know!

Thank you for your contributions.
This has been automatically marked as stale because it has had no activity for 180 days.
If this is still important to you, we ask that you leave a comment below. Your comment can be as simple as "still important to me". This lets people see that at least one person still cares about this. Someone will have to do this at most twice a year if there is no other activity.
Here are suggestions that might help resolve this more quickly:

1. Search for maintainers and people that previously touched the
   related code and @ mention them in a comment.
2. Ask on the NixOS Discourse. 3. Ask on the #nixos channel on
   irc.freenode.net.

still important to me, and in theory awaiting a response. I'll take another whack at this soon i guess.

The vim plugin list supports aliasing, so you can define a custom name for your plugin. Why do you want to pin the plugin to a specific repository version? That way you lose the benefit of regular semi-automatic updates.

I marked this as stale due to inactivity. → More info

if you still want to add this then follow https://nixos.org/manual/nixpkgs/stable/#adding-new-plugins-to-nixpkgs