personal blog
git clone git://
Log | Files | Refs | README

commit ca97fd173aa58a83024518175051a4811440f3ad
parent c0c4d9aa3f775a9c7f524ab448de9134cb68bb8b
Author: pyratebeard <>
Date:   Mon, 28 Feb 2022 23:04:46 +0000

Merge branch 'sed'

Aentry/ | 26++++++++++++++++++++++++++
1 file changed, 26 insertions(+), 0 deletions(-)

diff --git a/entry/ b/entry/ @@ -0,0 +1,26 @@ +If you have used `sed` then you have used the `/` delimiter +``` +sed s/foo/bar/g file +``` + +You will also probably be aware the need to escape any slash in the string you're trying to match, for example matching `f/o/o` would be +``` +sed s/f\/o\/o/b\/a\/r/g file +``` + +What you may not know is you can use different delimiters to save yourself escaping any occurrence of slash in the string. + +``` +sed s%foo%bar%g file +sed 's|foo|bar|g' file +sed 's foo bar g' file +``` + +Note that some delimiters require quotes. Any occurrence of your chosen delimiter in the string will have to be escaped. + +According to section 4.3 of the `sed` Info document you should be able to use "any single character", giving you a lot of options to chose from in order to avoid all the escaping. To read this section of the Info document incant +``` +info sed -n "regexp addresses" +``` + +Do you have a preferred delimiter or do you like a bit of variety?