The Nix language and package manager is now quite a large project (nixpkgs is of the largest and most active projects on GitHub, see https://github.com/NixOS/nixpkgs). It uses a domain-specific language for configuration. This PR adds syntax for the language.
The syntax is pulled from https://github.com/LnL7/vim-nix which is under MIT license. I have included attribution to the original author and a referred back to the GitHub repository. I reached out to the maintainer a few months ago to ask about including their code in vim. I got no response (LnL7/vim-nix#47), so I think it should be ok to proceed including this PR.
Note that I found a maintainer for the syntax file that is not me: @equill (ja...@electronic-quill.net) volunteered as the contact who is listed as maintainer in runtime/syntax/nix.vim.
@equill would you mind acknowledging that your contact information is correct and that you will be the point of contact for the Nix syntax highlighting?
https://github.com/vim/vim/pull/11646
(1 file)
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
I confirm of my own free will that I have indeed volunteered to be the maintainer/contact for this.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
Can you please also add an entry in .github/CODEOWNERS ?
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
Yes I can, though I'll be out till Monday.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
@jsoo1 pushed 1 commit.
—
View it on GitHub or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()
Ok I've added @equill as owner of runtime/syntax/nix.vim. I think there may be other nix support files that could be pulled from https://github.com/LnL7/vim-nix but I just don't know enough about vim to do the work.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
Thanks, I'll include it.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
Closed #11646.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
Noticed afterwards: The file uses line continuation, it should set the 'cpo' option and restore it.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
Noticed afterwards: The file uses line continuation, it should set the 'cpo' option and restore it.
Do you want a separate patch for that? If so, @equill would you mind doing the honors?
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
Noticed afterwards: The file uses line continuation, it should set the 'cpo' option and restore it.
Do you want a separate patch for that? If so, @equill would you mind doing the honors?
Sure, will do. Sorry about the slow response; I'm in transit and very jet-lagged.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()