> On Nov 29, 2018, at 6:27 AM, Yagamy Light <[email protected]> wrote: > > I recently migrated my workflow from a mess that is grep, sed, and perl, all > with different options, incompatible behavior and regexps, to just ack and > perl¹. I'm happy so far, but there's one thing I miss: ability for "ack" to > execute a command on files with matches. This can be worked around with > xargs, e.g.: > > ack -l --print0 pattern | xargs -r0 perl -i -pe 's/pattern/replacement/g'
Sorry, no, ack won’t be adding an functionality to execute anything. Executing based on results or doing edits to the files (another common request) are beyond what I want ack to be doing. I want ack to be entirely read-only and to not do anything that could potentially be destructive. Andy -- You received this message because you are subscribed to the Google Groups "ack users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/ack-users. For more options, visit https://groups.google.com/d/optout.
