When misspelling fuck and trying to fuck it, fuck fucks itself continuously. I don't know if it's a bug or feature.
max@Gotthold ~$ guck 22:00:26
fish: Unknown command 'guck'
(127) max@Gotthold ~$ fuck 22:00:29
fuck
fuck
fuck
fuck
fuck
fuck
fuck
fuck
fuck
fuck
fuck
fuck
fuck
^CTraceback (most recent call last):
File "/usr/local/bin/thefuck", line 5, in <module>
from pkg_resources import load_entry_point
File "build/bdist.macosx-10.10-x86_64/egg/pkg_resources/__init__.py", line 34, in <module>
File "/usr/local/Cellar/python/2.7.10/Frameworks/Python.framework/Versions/2.7/lib/python2.7/platform.py", line 1383, in <module>
r'([\w.+]+)\s*'
File "/usr/local/Cellar/python/2.7.10/Frameworks/Python.framework/Versions/2.7/lib/python2.7/re.py", line 194, in compile
return _compile(pattern, flags)
File "/usr/local/Cellar/python/2.7.10/Frameworks/Python.framework/Versions/2.7/lib/python2.7/re.py", line 249, in _compile
p = sre_compile.compile(pattern, flags)
File "/usr/local/Cellar/python/2.7.10/Frameworks/Python.framework/Versions/2.7/lib/python2.7/sre_compile.py", line 576, in compile
code = _code(p, flags)
File "/usr/local/Cellar/python/2.7.10/Frameworks/Python.framework/Versions/2.7/lib/python2.7/sre_compile.py", line 558, in _code
_compile_info(code, p, flags)
File "/usr/local/Cellar/python/2.7.10/Frameworks/Python.framework/Versions/2.7/lib/python2.7/sre_compile.py", line 437, in _compile_info
lo, hi = pattern.getwidth()
File "/usr/local/Cellar/python/2.7.10/Frameworks/Python.framework/Versions/2.7/lib/python2.7/sre_parse.py", line 158, in getwidth
for op, av in self.data:
KeyboardInterrupt
Another duplicate of #221. I'm almost happy with a reasonably good solution to this problem.
This issue is fixed by https://github.com/nvbn/thefuck/commit/96fe1e77b3cfacb5e2bb8e8568a5a515f3870ebf and can be closed.
I have the same problem on Mac OS X with zsh,I tried to install thefuck(version 1.46) from pip and brew,but both of them fuck themselves.Does the patch in 96fe1e7 included in version 1.46? @scorphus
No, 1.46 does not include the fix. It's yet to be released.
@maxried can you please confirm this issue is addressed in the last release?
Confirmed. Thanks :+1:
Superb! Can you please close this issue? Thank you!
This might be the issue report of the year.
Maybe @nvbn can close the issue himself, since @maxried doesn't seem to be very active around here, and has confirmed the resolution.
Funny issue, lol
Most helpful comment
This might be the issue report of the year.