query: sed escape /var/run/saslauthd
positive_passages.docid: 153258
positive_passages.text: Find the line number which contains the pattern using custom regex delimiter
negative_passages.docid: 77828
negative_passages.text: Can sed save its output to a file?
negative_passages.docid: 42244
negative_passages.text: Replace \n by a newline in sed portably
negative_passages.docid: 116024
negative_passages.text: Simple find and replace with sed
negative_passages.docid: 39116
negative_passages.text: sed : Ignore line starting whitespace for match
negative_passages.docid: 140924
negative_passages.text: Unix command sed replace in a variable
negative_passages.docid: 12642
negative_passages.text: sed command not giving proper output for regular expression used
negative_passages.docid: 116592
negative_passages.text: Make multiple edits with a single call to sed
negative_passages.docid: 30421
negative_passages.text: Escape a string for a sed replace pattern
negative_passages.docid: 25046
negative_passages.text: ^@^@ character in syslog
negative_passages.docid: 19763
negative_passages.text: Error with sed unterminated s command in bash
negative_passages.docid: 157583
negative_passages.text: When to use bash ANSI C style escape, e.g. $'\n'
negative_passages.docid: 65529
negative_passages.text: How do I escape the wildcard/asterisk character in bash?
negative_passages.docid: 136862
negative_passages.text: How to use a bash script variable with sed
negative_passages.docid: 13180
negative_passages.text: How do I fix "$'\r': command not found" errors running Bash scripts in WSL?
negative_passages.docid: 10632
negative_passages.text: sed regular expression behaving differently than in vim and perl?
negative_passages.docid: 11072
negative_passages.text: Can sed replace new line characters?