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
neovim-gtk: init at 0.1.1 #36109
neovim-gtk: init at 0.1.1 #36109
Conversation
In theory the package also requires a wrapper since nvim is not in PATH. |
description = "GTK ui for neovim written in rust using gtk-rs bindings. With ligatures support."; | ||
homepage = https://github.com/daa84/neovim-gtk; | ||
license = with licenses; [ gpl3 ]; | ||
platforms = platforms.all; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you want to maintain this package?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not really, I don't have any expertise in Rust and it was more because I wanted to try this UI. I might change my mind if I end up using it. Thanks for the icon fix.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we really accept packages without maintainers? If it is in the tree, someone will have to maintain it or it will become outdated soon.
If user just wants to share an expression, opening an issue or pull request should be enough.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes. We have too many unmaintained packages. Probably someone will pick it up eventually.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would say it is a problem. How often does someone pick up a package to maintain it? I would say a large fraction of packages is unmaintained, only occasionally being updated by a random passer-by discovering Repology. This leads to burn-outs of either the passers-by or the core maintainers reviewing the PRs.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nixos makes it kinda hard to try programs since you need to know nix to create the packages instead of just relying on the typical rust or python ecosystem. It's also difficult to ask for perfect packages from the start (like the wrapping thing, running the tests). I believe we need an overlay with a lower entry bar than nixpkgs, close to wiki-based (since the maintainer resource is scarce).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have not yet concrete ideas, how this could look like. But I have created the repository: https://github.com/nixos-users/NUR/tree/master
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
With github you still need someone to accept the PRs. Maybe a searchengine to search across different (user) overlays could work better, kind of what luarocks.org does. There is a default "root" repository but you can expand your search with user channels.
For instance I have a few nix packages available locally I don't mind making public but that don't meet yet nixos standards (ns-3/lkl improvements/castxml/pygccxml/mptcpanalyzer etc).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The idea was to accept make this an automatic registration process, maybe not even through the github ui but version controlled and only keep a central list of overlays a user can subscribe.
Basically to improve discovery and provide a communication channel between consumer and producer of an overlay and also to make adding/removing overlays easier.
neovim ui that supports ligatures.
Success on x86_64-linux (full log) Attempted: neovim-gtk Partial log (click to expand)
|
Failure on x86_64-linux (full log) Attempted: neovim-gtk Partial log (click to expand)
|
Failure on aarch64-linux (full log) Attempted: neovim-gtk Partial log (click to expand)
|
Failure on aarch64-linux (full log) Attempted: neovim-gtk Partial log (click to expand)
|
@GrahamcOfBorg build neovim-gtk |
Failure on x86_64-linux (full log) Attempted: neovim-gtk Partial log (click to expand)
|
Failure on x86_64-darwin (full log) Attempted: neovim-gtk Partial log (click to expand)
|
Failure on aarch64-linux (full log) Attempted: neovim-gtk Partial log (click to expand)
|
This is an updated version of it: ebf6538 |
neovim ui that supports ligatures.
As usual with gtk applications, I don't have icons (be it libreoffice or other gtk apps)
First time packaging a rust program, it seems to compile quite a bit of stuff.
build-use-sandbox
innix.conf
on non-NixOS)nix-shell -p nox --run "nox-review wip"
./result/bin/
)