Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upstream syntax highlighting? #47

Closed
jsoo1 opened this issue Sep 7, 2022 · 7 comments
Closed

Upstream syntax highlighting? #47

jsoo1 opened this issue Sep 7, 2022 · 7 comments

Comments

@jsoo1
Copy link

jsoo1 commented Sep 7, 2022

Hello! Thank you for vim-nix! Would you be alright if someone were to try to upstream the syntax highlighting from your plugin into {neo,}vim?

@jsoo1
Copy link
Author

jsoo1 commented Sep 8, 2022

According to the vim documentation on the subject some maintainer would be listed at the top of the syntax file who would send updated versions to Bram. For example, see the haskell syntax file.

Edit: To be clear, I wouldn't expect LnL7 to be the maintainer.

@equill
Copy link

equill commented Sep 12, 2022

I'm willing to maintain that bridge, fwiw.

@jsoo1
Copy link
Author

jsoo1 commented Dec 1, 2022

I think if enough time goes by I will put in a patch to the vim tree naming you @equill as the point of contact. Because this plugin is MIT licensed I believe it should suffice to keep a copy of the license and attribution to LnL7 in the upstream plugin.

@equill
Copy link

equill commented Dec 1, 2022

That works for me. Just give me a heads-up when you've done it, and I'll pick it up from there.

@jsoo1
Copy link
Author

jsoo1 commented Dec 10, 2022

As of vim/vim@86b4816 the syntax from vim-nix is in the vim tree. Thank you again to @equill and @LnL7 .

@jsoo1 jsoo1 closed this as completed Dec 10, 2022
@LnL7
Copy link
Owner

LnL7 commented Dec 23, 2022

Thanks for looking into this! I thought about this at some point but that was rather early on and I figured somebody would make a better package at some point 😁 since there are still some problems with indentation.

Some thoughts:
Depending on what gets added to vim-nix, it might make sense to only upstream the syntax/indentation and not commands, etc. No idea what the approach is for upstream vim.
Once nixpkgs is updated it might be good to get rid of some of the extra customization that happens there, nog sure if that's still in place.

@jsoo1
Copy link
Author

jsoo1 commented Dec 31, 2022

Thanks for looking into this! I thought about this at some point but that was rather early on and I figured somebody would make a better package at some point 😁 since there are still some problems with indentation.

You're welcome and thank you for all your work in the nix ecosystem!

I am pretty sure vim-nix remains the de-facto standard 😄. Ah, how software evolves, huh?

Not to worry, though, only the syntax highlighting made it upstream. Though indentation could be nice, should it get fixed 😃.

Some thoughts: Depending on what gets added to vim-nix, it might make sense to only upstream the syntax/indentation and not commands, etc.

I agree. I'm not even sure what kind of commands and extras would be accepted upstream.

No idea what the approach is for upstream vim. Once nixpkgs is updated it might be good to get rid of some of the extra customization that happens there, nog sure if that's still in place.

Good call. I can't recall but I did see one recent PR which spurred some of this work.

ncfavier added a commit to ncfavier/nixpkgs that referenced this issue Jun 6, 2023
Vim 9 includes syntax highlighting for nix files, but not the
ftplugin/indent parts of vim-nix so we still include those.

LnL7/vim-nix#47
vim/vim#11646
ncfavier added a commit to ncfavier/nixpkgs that referenced this issue Jun 6, 2023
Vim 9 includes syntax highlighting for nix files, but not the
ftplugin/indent parts of vim-nix so we still include those.

LnL7/vim-nix#47
vim/vim#11646
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants