kamp: init at 0.2.1

[erikeah]

Kamp, as described from author, is a tool to control Kakoune editor from the command line.
https://github.com/vbauerster/kamp

Things done

• Built on platform(s)
  • x86_64-linux
  • aarch64-linux
  • x86_64-darwin
  • aarch64-darwin
• For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)
  • sandbox = relaxed
  • sandbox = true
• Tested, as applicable:
  • NixOS test(s) (look inside nixos/tests)
  • and/or package tests
  • or, for functions and "core" functionality, tests in lib/tests or pkgs/test
  • made sure NixOS tests are linked to the relevant packages
• Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
• Tested basic functionality of all binary files (usually in ./result/bin/)
• 24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)
  • (Package updates) Added a release notes entry if the change is major or breaking
  • (Module updates) Added a release notes entry if the change is significant
  • (Module addition) Added a release notes entry if adding a new NixOS module
• Fits CONTRIBUTING.md.

---

Add a 👍 reaction to pull requests you find important.

[zimeg]

Thanks for joining us with contributions to nixpkgs! Super exciting!! 🎉

This is a neat package to add and I've left some comments to help align with nixpkgs conventions I'm aware of with reference to more information. 📚

[Atemu]

Diff LGTM.

Result of nixpkgs-review pr 347089 run on x86_64-linux 1

1 package built:

• kamp

I'd now like to be convinced that the package actually works as intended. Do you have a quick and easy way for us non-users to verify this or perhaps know another user who can easily verify that this works?

[erikeah]

Diff LGTM.

Result of nixpkgs-review pr 347089 run on x86_64-linux 1
1 package built:

I'd now like to be convinced that the package actually works as intended. Do you have a quick and easy way for us non-users to verify this or perhaps know another user who can easily verify that this works?

Of course, apart from the version check nix run .#kamp -- --version you could also use kamp with kakoune by checking out the branch and running:

nix run .#kakoune -- -e "$(nix run .#kamp -- init)"

Kakoune client should be attached now and command kamp-connect must be available by hitting semicolon.

[Atemu]

Nothing happens when I press semicolon. I can run it via :kamp-connect but I have no idea what it's supposed to do.

[erikeah]

@Atemu , The existence of kamp-connect is indeed part of the feature, because kamp init writes to stdout the needed configuration to allow kamp-connect command to be available in kakoune.

If you would like to go further you could create ~/.config/kak/kakrcfile with this config:

eval %sh{kamp init}

Checkout the branch and execute:

1. nix shell .#kamp .#kakoune .#fzf .#bat
2. kak
3. :e flake.nix
4. :e README.md
5. :kamp-connect terminal kamp-buffers # This will spot another terminal with fzf which will allow you to choose between currently open buffers.
6. Select one buffer (Navigate with C-n and C-p and hit Enter to choose)
7. The selected buffer must be visible in kakoune now.

[erikeah]

Which are next steps to follow to get merged?

[Atemu]

The steps you've given are a bit too much setup for me to realistically follow as a reviewer not interested in the component.

I was able to see it available in kakoune and I trust you tested this to be working fine, so I think this is good to go.