-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crash when using backspace for replace #34
Comments
This also happens in bulky 2.1. To reproduce it, it is necessary to use it from nemo. Select any two files, call rename via RMB and enter a backslash into the "Replace:" line (in a german version this is called "Ersetzen:"). If you call it from the command line with e.g. "bulky *", you get a permanent message |
The program enters infinite loop when the user adds a backslash at the end of a string in "replace" field. It happens because reg.sub throws an exception when it sees a backslash at the end of "replace" variable. The fix was already implemented for the case where regular expression replacement is enabled - catch regex exception and return unchanged string.
The program enters infinite loop when the user adds a backslash at the end of a string in "replace" field. It happens because reg.sub throws an exception when it sees a backslash at the end of "replace" variable. The fix was already implemented for the case where regular expression replacement is enabled - catch regex exception and return unchanged string.
Bulky 2.1 Same problem with entering a backslash character ( |
A fix has already been implemented but a new version was not released up to now. I replaced my /usr/lib/bulky/bulky.py with the file https://github.com/linuxmint/bulky/blob/master/usr/lib/bulky/bulky.py and now it works without a crash. |
Thank you, that worked! |
I think we can close this issue as it has been fixed with the pull request #47 |
bulky 1.8 crashes, when I enter a backspace character in the replacement line without activating "regular expression" before. Also, if a backspace is present in the replace-field and a unselect regular expressions afterwards, it crashed (it hangs, no reaction, must be killed)
The text was updated successfully, but these errors were encountered: