fix: handle invalid regex gracefully in search #1054
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Fixes #1038
This PR addresses the crash report dialog that appears when searching with an invalid regex pattern in Terminator.
Problem
When a user enters an invalid regex pattern in the search bar (e.g.,
Target(with an unclosed parenthesis), a GLib.Error exception is raised during regex compilation, which triggers a crash report dialog. While the application continues to run (non-fatal crash), this creates a poor user experience.Solution
The fix wraps the
GLib.Regex()compilation call in a try-except block to gracefully handle invalid regex patterns:GLib.Errorexceptions during regex compilationdbg()for troubleshootingChanges
terminatorlib/searchbar.py:GLib.Regex()compilation (lines 224-233)Testing
The fix handles the exact reproduction case from #1038:
Target(no longer shows a crash dialogBehavior
Before: Invalid regex → Crash dialog → User confusion
After: Invalid regex → Visual feedback → Disabled search → No crash dialog
Automated contribution via github-ai-contributor