You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a recurring problem with SIGINT being ignored in my shells, which I've been able to narrow down to zsh-histdb. Everything works as expected, except ctrl-c suddenly stops working in the shell. Executing trap INT {} restores the normal behaviour until it happens again. It's sporadic, but I can reproduce it very easily in about 5 seconds immediately after starting a shell.
I was using histdb for years before this showed up, but I can't pinpoint when it did. I've been able to reproduce this with a clean environment and only zsh-histdb, so this is definitely the cause.
I've not been able to reproduce it in the macOS Terminal.app, which is interesting, only in iTerm.
It sounds similar to #83, but probably something different.
Environment
Latest version (90a6c10).
SQLite shipped with macOS (3.43.2 right now) or latest version 3.46.0 via Homebrew.
iTerm 3.5.3
The text was updated successfully, but these errors were encountered:
I have a recurring problem with
SIGINT
being ignored in my shells, which I've been able to narrow down to zsh-histdb. Everything works as expected, except ctrl-c suddenly stops working in the shell. Executingtrap INT {}
restores the normal behaviour until it happens again. It's sporadic, but I can reproduce it very easily in about 5 seconds immediately after starting a shell.I was using histdb for years before this showed up, but I can't pinpoint when it did. I've been able to reproduce this with a clean environment and only zsh-histdb, so this is definitely the cause.
I've not been able to reproduce it in the macOS Terminal.app, which is interesting, only in iTerm.
It sounds similar to #83, but probably something different.
Environment
90a6c10
).The text was updated successfully, but these errors were encountered: