utility/jupynvim: init

[jack-thesparrow]

Sanity Checking

• I have updated the changelog as per my changes
• I have tested, and self-reviewed my code
• My changes fit guidelines found in hacking nvf
• Style and consistency
  • I ran Alejandra to format my code (nix fmt)
  • My code conforms to the editorconfig configuration of the project
  • My changes are consistent with the rest of the codebase
• If new changes are particularly complex:
  • My code includes comments in particularly complex areas
  • I have added a section in the manual
  • I have included a migration guide
• Package(s) built:
  • .#nix
  • .#maximal
  • .#docs-html
  • .#docs-linkcheck
• Tested on platform(s)
  • x86_64-linux
  • aarch64-linux
  • x86_64-darwin
  • aarch64-darwin

[github-actions]

🚀 Live preview deployed from c5cad7e

View it here:

Debug Information

Triggered by: jack-thesparrow

HEAD at: feat/jupynvim

Reruns: 3984

[NotAShelf]

I left some minor comments. Typically we expect plugins to expose options that take to 3rd party tools, e.g, something like chafa_path in the setup table which we can use to allow overriding. If not, this should be brought up with upstream. If such an option exists, please prefer it over adding packages to the closure.

[jack-thesparrow]

Done with the changes.

[NotAShelf]

@jack-thesparrow I'd like a disclosure on how LLMs were used in this PR. It is no longer a question they were used, but a question of how they were used. While we don't have a clear LLM policy; I cannot, in good faith, merge a PR where the author has put their agent on the task of responding to review comments. This is disrespectful to both my co-maintainers, who have gracefully taken time of their day to review, and the users who expect us to deliver quality.

[jack-thesparrow]

@jack-thesparrow I'd like a disclosure on how LLMs were used in this PR. It is no longer a question they were used, but a question of how they were used. While we don't have a clear LLM policy; I cannot, in good faith, merge a PR where the author has put their agent on the task of responding to review comments. This is disrespectful to both my co-maintainers, who have gracefully taken time of their day to review, and the users who expect us to deliver quality.

I understand it now sir, and i sincerely apologize for it. I accept that i have used LLMs in this PR and have accepted the changes personally into the PR after checking them. I am sorry to hurt your sentiments. I use NVF as my personal config, so i thought of contributing. I love this project and will still contribute to it, but next time it will be written by me.I have learned my lesson and i am ready to accept your decision on whether to merge or not @NotAShelf :)

[snoweuph]

@jack-thesparrow I'd like a disclosure on how LLMs were used in this PR. It is no longer a question they were used, but a question of how they were used. While we don't have a clear LLM policy; I cannot, in good faith, merge a PR where the author has put their agent on the task of responding to review comments. This is disrespectful to both my co-maintainers, who have gracefully taken time of their day to review, and the users who expect us to deliver quality.

I understand it now sir, and i sincerely apologize for it. I accept that i have used LLMs in this PR and have accepted the changes personally into the PR after checking them. I am sorry to hurt your sentiments. I use NVF as my personal config, so i thought of contributing. I love this project and will still contribute to it, but next time it will be written by me.I have learned my lesson and i am ready to accept your decision on whether to merge or not @NotAShelf :)

You seem to not have understood the main point. Its the same as in #1778
Its about disclosure in which way and context it was used.

[snoweuph]

@jack-thesparrow I'd like a disclosure on how LLMs were used in this PR. It is no longer a question they were used, but a question of how they were used. While we don't have a clear LLM policy; I cannot, in good faith, merge a PR where the author has put their agent on the task of responding to review comments. This is disrespectful to both my co-maintainers, who have gracefully taken time of their day to review, and the users who expect us to deliver quality.

I understand it now sir, and i sincerely apologize for it. I accept that i have used LLMs in this PR and have accepted the changes personally into the PR after checking them. I am sorry to hurt your sentiments. I use NVF as my personal config, so i thought of contributing. I love this project and will still contribute to it, but next time it will be written by me.I have learned my lesson and i am ready to accept your decision on whether to merge or not @NotAShelf :)

You seem to not have understood the main point. Its same as in #1778 Its about disclosure in which way and context it was used.
This is the last reminder: disclose us HOW and for WHAT LLMs where used and in which capacity

[jack-thesparrow]

@jack-thesparrow I'd like a disclosure on how LLMs were used in this PR. It is no longer a question they were used, but a question of how they were used. While we don't have a clear LLM policy; I cannot, in good faith, merge a PR where the author has put their agent on the task of responding to review comments. This is disrespectful to both my co-maintainers, who have gracefully taken time of their day to review, and the users who expect us to deliver quality.

I understand it now sir, and i sincerely apologize for it. I accept that i have used LLMs in this PR and have accepted the changes personally into the PR after checking them. I am sorry to hurt your sentiments. I use NVF as my personal config, so i thought of contributing. I love this project and will still contribute to it, but next time it will be written by me.I have learned my lesson and i am ready to accept your decision on whether to merge or not @NotAShelf :)

You seem to not have understood the main point. Its same as in #1778 Its about disclosure in which way and context it was used. This is the last reminder: disclose us HOW and for WHAT LLMs where used and in which capacity

I used LLMs it to write grep commands to skim through the existing codebase to learn how existing plugins were implemented, for writing the default keybinds, and replying to the Github reviews.