S&R: Only add maximum 70 characters context before & after match.
Description
Description
Details
Details
- Committed
sars Dec 6 2018, 3:51 PM - Parents
- R40:638cb985cd9e: S&R: Make one transaction for the whole replace to speed up things
- Branches
- Unknown
- Tags
Comment Actions
Can you add an option to turn off this feature?
And option for max length?
Hi, what's the benefit of this change?
Why max length is 70? It's so short on 4K monitor.
When analyze huge log file with timestamp, I can not get full line information
Can you add an option to turn off this feature?
And option for max length?
Comment Actions
Imagine you have a "minimized" javascript or XML file. You basically have the whole file on one line. This can be thousands of characters on a line. If you now search for a fairly common word in the minimized code, you would duplicate the huge line as many times as you get matches.
The context length was added so that you only get a finite amount of characters per match.
I assume that in 99,99% of the time, having configuration for this context length is not worth it.
A workaround for your problem could be to include the timestamp in the search expression (regular expression)
\d\d-\d\d\s\d\d:\d\d.*<your search here>
Hope this helps,
/Kåre
Comment Actions
For minimized js/xml, I prefer pretty it first.
The timestamp I mentioned is just an example.
I need the full line most time when I analyze such kernel log, adb log.
This seems a workaroud
^.*keyword
But not convenient.
So,could you please add an option to turn off this feature at least?