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
I'm new to the tool but saw in the command line help:
-rt, --replace-text <expressions-file>
filter content of files, replacing matched text. Match expressions should be listed in the file, one expression per line - by default, each expression is treated as a literal, but 'regex:' & 'glob:' prefixes are supported, with '==>' to specify a replacement string other than the default of '***REMOVED***'.
I stumbled quit a bit over the ==> (original I had a white space on either side of the arrow). It's not even mentioned on the docs website as a possibility. Could we update the documentation website to add a find and replace example? It probably wouldn't hurt to add a glob and regexp examples too, since I noticed those are also absent.
I'm new to the tool but saw in the command line help:
-rt, --replace-text <expressions-file>
filter content of files, replacing matched text. Match expressions should be listed in the file, one expression per line - by default, each expression is treated as a literal, but 'regex:' & 'glob:' prefixes are supported, with '==>' to specify a replacement string other than the default of '***REMOVED***'.
I stumbled quit a bit over the ==> (original I had a white space on either side of the arrow). It's not even mentioned on the docs website as a possibility. Could we update the documentation website to add a find and replace example? It probably wouldn't hurt to add a glob and regexp examples too, since I noticed those are also absent.
Hi,
I'm new to the tool but saw in the command line help:
I stumbled quit a bit over the ==> (original I had a white space on either side of the arrow). It's not even mentioned on the docs website as a possibility. Could we update the documentation website to add a find and replace example? It probably wouldn't hurt to add a glob and regexp examples too, since I noticed those are also absent.
e.g.
password.txt
The text was updated successfully, but these errors were encountered: