You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It is clear why this happens - the replacement contains comma, so the regular expression matches the line again, replaces the comma with \n,, matches again, replaces the comma again to obtain \n\n,, etc... Eventually the python interpreter would run out of memory.
This is by design, replacement does not advance the position in the line, so that any subsequent colourifying rules/matches can be applied against the new line.
In ae79db5 I have applied a change that stops replacing after the first successful replace, so it should be fixed.
I have a log file in which I would like to replace
,
with\n,
.So, I put the following in a configuration file my.config:
and call it like
grcat my.config < some_logifle
.But this only results in high cpu load and grcat does not respond. I have to kill the process by force.
This also happens with things like:
or:
or simply:
This works, though:
python --version
gives me:Python 2.7.15
The text was updated successfully, but these errors were encountered: