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've found that rubocop-guard is breaking my ZSH terminal (but it is happening in Bash as well), especially after some error was printed to STDOUT. I had to exit from guard and run stty sane to reset the terminal every time when this happen. This issue is bothering me for 2 months, but I was suspecting guard-rspec which I am using as well.
After some research I knew that is some ANSI escaping issue and that it is happening somewhere around Guard::UI or Guard::Compat::UI. Today I first tried to disable the guard-rubocop and the problem went away, then I discovered the PR #19 which promotes upgrade to "new" Guard::Compat API and I give it a try. When I applied patch in #19 the problem went away as well.
The simplest way is just add gem rb-readline to your development Gemfile. I've encountered several situations in past hours which I am sure would end up with corrupted terminal, but with rb-readline it works ok.
I've found that
rubocop-guard
is breaking my ZSH terminal (but it is happening in Bash as well), especially after some error was printed to STDOUT. I had to exit from guard and runstty sane
to reset the terminal every time when this happen. This issue is bothering me for 2 months, but I was suspectingguard-rspec
which I am using as well.After some research I knew that is some ANSI escaping issue and that it is happening somewhere around
Guard::UI
orGuard::Compat::UI
. Today I first tried to disable theguard-rubocop
and the problem went away, then I discovered the PR #19 which promotes upgrade to "new"Guard::Compat
API and I give it a try. When I applied patch in #19 the problem went away as well.Before patch:
guard-rubocop (1.2.0)
guard (
> 2.0)> 0.20)rubocop (
After patch:
guard-rubocop (1.2.0-patched)
guard (
> 2.0)> 1.1)guard-compat (
rubocop (~> 0.20)
System info
The text was updated successfully, but these errors were encountered: