tldr/pages/common/sed.md

# sed

> Edit text in a scriptable manner.
> See also: `awk`, `ed`.
> More information: <https://www.gnu.org/software/sed/manual/sed.html>.

- Replace all `apple` (basic regex) occurrences with `mango` (basic regex) in all input lines and print the result to `stdout`:

`{{command}} | sed 's/apple/mango/g'`

- Execute a specific script [f]ile and print the result to `stdout`:

`{{command}} | sed -f {{path/to/script.sed}}`

- Replace all `apple` (extended regex) occurrences with `APPLE` (extended regex) in all input lines and print the result to `stdout`:

`{{command}} | sed -E 's/(apple)/\U\1/g'`

- Print just a first line to `stdout`:

`{{command}} | sed -n '1p'`

- Replace all `apple` (basic regex) occurrences with `mango` (basic regex) in all input lines and save modifications to a specific file:

`sed -i 's/apple/mango/g' {{path/to/file}}`
Add doc for sed(1) 2013-12-11 10:50:11 +00:00			`# sed`

sed: show usage of a print command (#2154) 2018-06-26 16:19:31 +01:00			`> Edit text in a scriptable manner.`
sed: refresh/add pages (#7931) 2022-11-12 13:05:16 +00:00			> See also: `awk`, `ed`.
common/*: replace man.archlinux.org (#7860) 2022-03-09 04:28:57 +00:00			`> More information: <https://www.gnu.org/software/sed/manual/sed.html>.`
Add doc for sed(1) 2013-12-11 10:50:11 +00:00
sed: refresh/add pages (#7931) 2022-11-12 13:05:16 +00:00			- Replace all `apple` (basic regex) occurrences with `mango` (basic regex) in all input lines and print the result to `stdout`:
Add doc for sed(1) 2013-12-11 10:50:11 +00:00
sed: refresh/add pages (#7931) 2022-11-12 13:05:16 +00:00			`{{command}} \| sed 's/apple/mango/g'`
Add doc for sed(1) 2013-12-11 10:50:11 +00:00
sed: refresh/add pages (#7931) 2022-11-12 13:05:16 +00:00			- Execute a specific script [f]ile and print the result to `stdout`:
Sed: adds replace before matching sample Something I find myself doing more and more is to match on a line instead of trying to match all I want with `{{find}}`. So in a file like: ```erl { riak_core, [ { {riak_ip, "127.0.0.1"}, %% ... }, %% ... ] ``` Instead of replacing that ip by doing `sed 's/riak_ip,"127\.0\.0\.1/riak_ip,"$NEW_IP/'`, I do `sed '/riak_ip/s/127\.0\.0\.1/$NEW_IP'`. 2016-02-27 13:23:24 +00:00
sed: refresh/add pages (#7931) 2022-11-12 13:05:16 +00:00			`{{command}} \| sed -f {{path/to/script.sed}}`
Sed: adds replace before matching sample Something I find myself doing more and more is to match on a line instead of trying to match all I want with `{{find}}`. So in a file like: ```erl { riak_core, [ { {riak_ip, "127.0.0.1"}, %% ... }, %% ... ] ``` Instead of replacing that ip by doing `sed 's/riak_ip,"127\.0\.0\.1/riak_ip,"$NEW_IP/'`, I do `sed '/riak_ip/s/127\.0\.0\.1/$NEW_IP'`. 2016-02-27 13:23:24 +00:00
sed: refresh/add pages (#7931) 2022-11-12 13:05:16 +00:00			- Replace all `apple` (extended regex) occurrences with `APPLE` (extended regex) in all input lines and print the result to `stdout`:
Add doc for sed(1) 2013-12-11 10:50:11 +00:00
sed: refresh/add pages (#7931) 2022-11-12 13:05:16 +00:00			`{{command}} \| sed -E 's/(apple)/\U\1/g'`
Add doc for sed(1) 2013-12-11 10:50:11 +00:00
sed: refresh/add pages (#7931) 2022-11-12 13:05:16 +00:00			- Print just a first line to `stdout`:
Add doc for sed(1) 2013-12-11 10:50:11 +00:00
sed: refresh/add pages (#7931) 2022-11-12 13:05:16 +00:00			`{{command}} \| sed -n '1p'`
Adding a line for sed for making multiple replacements in one command. 2014-03-27 18:27:35 +00:00
sed: refresh/add pages (#7931) 2022-11-12 13:05:16 +00:00			- Replace all `apple` (basic regex) occurrences with `mango` (basic regex) in all input lines and save modifications to a specific file:
sed: Add example to delete lines (#2596) 2018-11-16 14:11:22 +00:00
sed: refresh/add pages (#7931) 2022-11-12 13:05:16 +00:00			`sed -i 's/apple/mango/g' {{path/to/file}}`