-
-
Notifications
You must be signed in to change notification settings - Fork 14.8k
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
kakoune-lsp: 16.0.0 -> 17.1.1 #302761
kakoune-lsp: 16.0.0 -> 17.1.1 #302761
Conversation
Result of 1 package built:
|
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.
Verified basic functionality (clangd
integration).
This (and also the current version of this package) needs a newer Kakoune version, it broke my configuration:
|
@2xsaiko Right, inlay stuff in kakoune-lsp ≥ 16 requires git (unreleased) Kakoune; but at least ≥ 17 (this PR, or anything including kakoune-lsp/kakoune-lsp@86ceae0) will tell you what’s wrong instead of crashing incomprehensibly. As far as cutting a release of Kakoune, we’re probably at the mercy of @mawww here as opposed to the Nixpkgs maintainerdom—you don’t usually get unreleased versions in Nixpkgs unless there’s no choice. |
To anyone who wants to use inlay diagnostics with the current stable version of Kakoune, add the following to the
I've been using this for a while with no issues. |
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 new version seems to work very well, including code actions when perl is not in PATH (which was previously broken).
what's blocking this from being merged? |
can we review and merge this? There is even an 17.1.1 out for a while. |
I've fixed the conflict. Can someone merge this finally? Once that's done it'd be a simple matter for someone to bump it from there to the latest version. |
bcf9c0c
to
8d9ed73
Compare
Correction: have now fixed the conflict without using the web UI (which somehow produced an incorrect commit). Should be good to go now. |
Thanks for keeping this patch running. I'm back in the saddle and looking to merge once a few things are tidied up. |
I'm not looking to make further changes on this, sorry. In the several months it took for anyone to actually look at this PR, I've entirely stopped using Nix on any of my machines, so this isn't really a priority for me now. |
Understood. Would you mind if I did so? |
You're welcome to! :) Please try to keep my authorship metadata intact, depending on how you go about this. |
I'll do my very best. 🙇🏻 |
Thanks! |
Funnily enough this broke basically immediately because of #332957 |
I can confirm the following update now makes it build. |
|
Description of changes
The Perl patch no longer applied, so along with creating a new version of it, I took the liberty to clean up the package overall.
Things done
nix.conf
? (See Nix manual)sandbox = relaxed
sandbox = true
nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD"
. Note: all changes have to be committed, also see nixpkgs-review usage./result/bin/
)Add a 👍 reaction to pull requests you find important.