John Kerl
John Kerl
@torbiak ``` echo 'x=[.o*o.]' | mlr put '$y=gsub($x, "\[", "LEFT")' x=[.o*o.],y=LEFT.o*o.] echo 'x=[.o*o.]' | mlr put '$y=gsub($x, ".", "ALL")' x=[.o*o.],y=ALLALLALLALLALLALLALL echo 'x=[.o*o.]' | mlr put '$y=gsub($x, "\.", "DOT")' x=[.o*o.],y=[DOTo*oDOT] echo...
Test case https://github.com/johnkerl/miller/commit/55209bfc5ccf2b1f5919ece26bb2425117ab2ac5 Comments https://github.com/johnkerl/miller/commit/9286f5a3b14bc603fe941a461abcfe5a5459d5ff More doc details about Miller regexes upcoming at https://johnkerl.org/miller6 (subsequent PRs)
@torbiak no ... the 'implicit r' would only apply for string literals in that position. To make this work with the `star_re = "\*"` example we'd need an 'explicit r'...
@torbiak another option would be to abandon the notion of 'implicit r' entirely, and only have 'explicit r' ... i'm not sure which approach follows the principle of least surprise...
I prefer option 1 personally ...
Good news is there's little backward behavior to protect so explicit-r would break almost nobody ... ... bad news is the one thing that does work is `\.` and explicit-r...
This issue is resolved in Miller 6 _except_ for the new feature-add of r-strings as discussed above -- probably a good candidate for 6.1.
Creating a separate issue to track this.
@seamusdemora sorry for the delay!
For handy reference here's a copy of your comment from https://github.com/johnkerl/miller/issues/212#issuecomment-754687472 ---- This is a [screen shot of the oscilloscope trace](https://imgur.com/a/oBx0I1N) with some notes that might help. Here's approx 20...