Comma runs software without installing it. [maintainers=@Artturin,@burke,@DavHau]
Find a file
2025-07-29 15:52:51 +03:00
.github Bump cachix/install-nix-action from 30 to 31 2025-03-17 11:19:02 +00:00
etc Install handlers in a location where they won't be autoloaded 2025-07-29 15:51:05 +03:00
src Move mangen above cache 2025-07-29 14:25:31 +03:00
.envrc rewrite in rust 2022-04-19 01:36:39 +03:00
.gitignore add .direnv to gitignore 2022-11-20 18:12:32 +02:00
Cargo.lock v2.3.3 2025-07-29 15:52:51 +03:00
Cargo.toml v2.3.3 2025-07-29 15:52:51 +03:00
default.nix Format 2025-07-13 20:27:22 +03:00
flake.lock flake.lock: Update 2025-07-19 14:59:03 +03:00
flake.nix Install handlers in a location where they won't be autoloaded 2025-07-29 15:51:05 +03:00
LICENSE Add LICENSE file, The license was already specified in the Cargo.toml 2024-11-27 20:31:54 +02:00
README.md Update README.md with cache instructions 2025-07-12 13:01:11 +01:00
release.sh Add quotes release.sh 2025-07-11 16:16:00 +03:00
shell.nix Format 2025-07-13 20:27:22 +03:00

comma

Comma runs software without installing it.

Basically it just wraps together nix shell -c and nix-index. You stick a , in front of a command to run it from whatever location it happens to occupy in nixpkgs without really thinking about it.

Installation

comma is in nixpkgs so you can install it just like any other package.

either install it in your nix environment

nix-env -f '<nixpkgs>' -iA comma

or add this snippet to your NixOS configuration.

environment.systemPackages = with pkgs; [ comma ];

Usage

, cowsay neato

Cache

Comma supports caching both the choices (i.e., once you select a derivation for a command, it will always return the same derivation) and paths (i.e., once the path is evaluated by Nix, we will always return the same path until it is GC'd). You can control those options by using --cache-level flag or COMMA_CACHING environment variable:

  • 0: completely disables caching
  • 1: only cache choices
  • 2 (default): also caches paths

Cache for path is the default since it makes subsequent usage of a command much faster:

$ hyperfine "./result/bin/comma --cache-level=1 ls" "./result/bin/comma --cache-level=2 ls"
Benchmark 1: ./result/bin/comma --cache-level=1 ls
  Time (mean ± σ):      1.050 s ±  0.021 s    [User: 0.540 s, System: 0.210 s]
  Range (min … max):    1.009 s …  1.075 s    10 runs

Benchmark 2: ./result/bin/comma --cache-level=2 ls
  Time (mean ± σ):       6.6 ms ±   1.0 ms    [User: 3.0 ms, System: 3.5 ms]
  Range (min … max):     5.8 ms …  11.3 ms    297 runs

  Warning: Statistical outliers were detected. Consider re-running this benchmark on a quiet system without any interferences from other programs. It might help to use the '--warmup' or '--prepare' options.

Summary
  ./result/bin/comma --cache-level=2 ls ran
  159.25 ± 23.44 times faster than ./result/bin/comma --cache-level=1 ls

However, it also means you may not run the most up-to-date version of a command, specially if you don't run Nix's garbage collector often. If this is an issue for you, set COMMA_CACHING=1.

Prebuilt index

https://github.com/Mic92/nix-index-database