No history was kept. zsh's defaults are SAVEHIST=0 and HISTSIZE=30, and there is no history file. The block now keeps 100k entries in ~/.zsh_history, shared between open shells.
Completion was never initialised. Nothing ran compinit, so only basic completion worked. The block now runs compinit with its cache in ~/.cache/zsh, and turns on menu selection.
Checked: zsh -n on the block; in a scratch home, 1715 completions load and history is set; module check passes all 74 manifests; zsh tests 16/16.
Found reviewing the shell on g14 (hq to-be 41):
- **No history was kept.** zsh's defaults are `SAVEHIST=0` and `HISTSIZE=30`, and there is no history file. The block now keeps 100k entries in `~/.zsh_history`, shared between open shells.
- **Completion was never initialised.** Nothing ran `compinit`, so only basic completion worked. The block now runs `compinit` with its cache in `~/.cache/zsh`, and turns on menu selection.
Checked: `zsh -n` on the block; in a scratch home, 1715 completions load and history is set; `module check` passes all 74 manifests; zsh tests 16/16.
zsh saves no history by default (SAVEHIST=0) and nothing called compinit, so
every machine had 30 lines of unsaved history and only basic completion.
Found reviewing the shell on its first machine (hq to-be 41).
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Found reviewing the shell on g14 (hq to-be 41):
SAVEHIST=0andHISTSIZE=30, and there is no history file. The block now keeps 100k entries in~/.zsh_history, shared between open shells.compinit, so only basic completion worked. The block now runscompinitwith its cache in~/.cache/zsh, and turns on menu selection.Checked:
zsh -non the block; in a scratch home, 1715 completions load and history is set;module checkpasses all 74 manifests; zsh tests 16/16.