home-manager/tests/modules/programs/zsh/history-substring-search.nix

{
  programs.zsh = {
    enable = true;
    historySubstringSearch = {
      enable = true;
      searchDownKey = "^[[B";
      searchUpKey = [ "^[[A" "\\eOA" ];
    };
  };

  # Written with regex to ensure we don't end up missing newlines in the future
  nmt.script = ''
    assertFileRegex home-files/.zshrc "^bindkey \"\^\[\[B\" history-substring-search-down$"
    assertFileRegex home-files/.zshrc "^bindkey \"\^\[\[A\" history-substring-search-up$"
    assertFileRegex home-files/.zshrc "^bindkey \"\\\\eOA\" history-substring-search-up$"
  '';
}
zsh: allow multiple bindings to history-substring-search (#3929) It's pretty common to need multiple bindings to history-substring-search, since different terminals will send different keys for up/down. This does not break back-compatibility, and introduces a new test 2023-04-29 07:53:09 -07:00			`{`
tests: rework derivation stubbing Instead of having to manually stub packages that should not be downloaded we instead automatically stub all packages (except a small list of whitelisted ones). Tests can re-introduce the real package by using the `realPkgs` module argument. 2025-01-31 21:24:47 +01:00			`programs.zsh = {`
			`enable = true;`
			`historySubstringSearch = {`
zsh: allow multiple bindings to history-substring-search (#3929) It's pretty common to need multiple bindings to history-substring-search, since different terminals will send different keys for up/down. This does not break back-compatibility, and introduces a new test 2023-04-29 07:53:09 -07:00			`enable = true;`
tests: rework derivation stubbing Instead of having to manually stub packages that should not be downloaded we instead automatically stub all packages (except a small list of whitelisted ones). Tests can re-introduce the real package by using the `realPkgs` module argument. 2025-01-31 21:24:47 +01:00			`searchDownKey = "^[[B";`
			`searchUpKey = [ "^[[A" "\\eOA" ];`
zsh: allow multiple bindings to history-substring-search (#3929) It's pretty common to need multiple bindings to history-substring-search, since different terminals will send different keys for up/down. This does not break back-compatibility, and introduces a new test 2023-04-29 07:53:09 -07:00			`};`
			`};`
tests: rework derivation stubbing Instead of having to manually stub packages that should not be downloaded we instead automatically stub all packages (except a small list of whitelisted ones). Tests can re-introduce the real package by using the `realPkgs` module argument. 2025-01-31 21:24:47 +01:00
			`# Written with regex to ensure we don't end up missing newlines in the future`
			`nmt.script = ''`
			`assertFileRegex home-files/.zshrc "^bindkey \"\^\[\[B\" history-substring-search-down$"`
			`assertFileRegex home-files/.zshrc "^bindkey \"\^\[\[A\" history-substring-search-up$"`
			`assertFileRegex home-files/.zshrc "^bindkey \"\\\\eOA\" history-substring-search-up$"`
			`'';`
zsh: allow multiple bindings to history-substring-search (#3929) It's pretty common to need multiple bindings to history-substring-search, since different terminals will send different keys for up/down. This does not break back-compatibility, and introduces a new test 2023-04-29 07:53:09 -07:00			`}`