Changes between Initial Version and Version 1 of Ticket #400, comment 5
- Timestamp:
- 09/26/16 15:51:01 (8 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #400, comment 5
initial v1 1 We can solve this by adding to the search dialog a "[x] Search over lines" checkbox what would turn off the `current_chr == '\n'`check I quoted in comment 4. This would make the text accumulate in one giant string instead of line-by-line (but we should set some limit in case one searches in a 20 terabyte file...).1 We can solve this by adding to the search dialog a "[x] Search over lines" checkbox what would turn off the "`current_chr == '\n'`" check I quoted in comment 4. This would make the text accumulate in one giant string instead of line-by-line (but we should set some limit in case one searches in a 20 terabyte file...). 2 2 3 If we detect a newline in the regexp, we'll search-over-lines automatically. But having a checkbox is good for the case one wants to search for things like `struct {.*?}`, where it's a dot that stands for a newline.3 If we detect a newline in the regexp, we'll search-over-lines automatically. But having a checkbox is good for the case one wants to search for things like "`struct {.*?}`", where it's a dot that stands for a newline.