@prusnak amended the commit message.

I'm afraid this will be overwritten next time someone updates the package set... We would need to fix the name of the repo itself

@jonringer Another option would be to special-case the script to avoid using the key vim and defaulting to owner-repo. So in this case dracula-vim would be the resulting key. There might be other plugins out there that have this issue.

I think this could lead to some odd behavior, I would like to hear from some others that use vim

cc @timokau @colemickens @Mic92 @teto

we could change vim-plugin-names format to be able to specify the nix attribute name. This is how I addressed it for the lua ecosystem (see https://github.com/NixOS/nixpkgs/blob/master/maintainers/scripts/luarocks-packages.csv , haskell has a similar .yaml configuration).
It may sound overkill but I believe we will eventually get there to specify a maintainer or pin a version when the need arises (some plugins are more complex than others, aka coc.nvim/unicode.vim etc).

At some point, we might want to standardize such a configuration file across the different "language packages to nix derivation" ecosystems.

I think having a mechanism to do some of the renaming makes sense

That was already implemented by @gjabell a while ago in 8eb8fa1. You can just specify dracula/vim as dracula-vim in vim-plugin-names.

That was already implemented by @gjabell a while ago in 8eb8fa1. You can just specify dracula/vim as dracula-vim in vim-plugin-names.

good point, I totally forgot about that indirection

@timokau @jonringer Does that mean I should just edit https://github.com/NixOS/nixpkgs/blob/master/pkgs/misc/vim-plugins/vim-plugin-names and submit a new PR? Do I have to run the update script myself or does the build do that?

you can see there's a similar example:

gruvbox-community/gruvbox as gruvbox-community

I would just edit it to say:

dracula/vim as dracula-vim

and then re-run the update.py