Closed mowgli closed 7 months ago
Don't believe this a zinit issue per se.
Show us your ices.
@mowgli,
@pschmitt is correct that this is unrelated to Zinit.
Please see these zsh-histdb
issues or open an issue there if your problem persists.
@mowgli,
Locking due to lack of activity.
What happened?
I often get the following error:
In case of a larger pipe I get that message multiple times. On other occasions I get the following error right after it:
The error always appears direct after the first command or pipe I do in the shell. I did not seen it later on.
Steps to reproduce
See above
Relevant output
Screenshots and recordings
See above
Operating System & Version
OS: linux-gnu | Vendor: debian | Machine: x86_64 | CPU: x86_64 | Processor: unknown | Hardware: x86_64
Zsh version
Doesn't apply as it was with many in the past. Currently 5.9
Terminal emulator
xterm
If using WSL on Windows, which version of WSL
None
Additional context
No response
Code of Conduct