Skip to main content
replaced http://vi.stackexchange.com/ with https://vi.stackexchange.com/
Source Link

Another alternative is ex, the predecessor to vi. It is actually the POSIX tool of choice for in-place scripted file editing; it is extraordinarily more flexible than sed -i and arguably even more portable than Perl. (If you stay outside of the Windows world, it's unarguably more portable than Perl.)

There is a relative dearth on this stackexchange of example commands using ex, at least compared with the plethora of example commands using sed, awk and Perl. However, I myself have delved extensively into the POSIX specs for ex and I've been beating the drum for it ever since. I've written many answers using ex both here and on the vi/Vim stackexchange:

Further reading:

Another alternative is ex, the predecessor to vi. It is actually the POSIX tool of choice for in-place scripted file editing; it is extraordinarily more flexible than sed -i and arguably even more portable than Perl. (If you stay outside of the Windows world, it's unarguably more portable than Perl.)

There is a relative dearth on this stackexchange of example commands using ex, at least compared with the plethora of example commands using sed, awk and Perl. However, I myself have delved extensively into the POSIX specs for ex and I've been beating the drum for it ever since. I've written many answers using ex both here and on the vi/Vim stackexchange:

Further reading:

Another alternative is ex, the predecessor to vi. It is actually the POSIX tool of choice for in-place scripted file editing; it is extraordinarily more flexible than sed -i and arguably even more portable than Perl. (If you stay outside of the Windows world, it's unarguably more portable than Perl.)

There is a relative dearth on this stackexchange of example commands using ex, at least compared with the plethora of example commands using sed, awk and Perl. However, I myself have delved extensively into the POSIX specs for ex and I've been beating the drum for it ever since. I've written many answers using ex both here and on the vi/Vim stackexchange:

Further reading:

replaced http://unix.stackexchange.com/ with https://unix.stackexchange.com/
Source Link

Another alternative is ex, the predecessor to vi. It is actually the POSIX tool of choice for in-place scripted file editing; it is extraordinarily more flexible than sed -i and arguably even more portable than Perl. (If you stay outside of the Windows world, it's unarguably more portable than Perl.)

There is a relative dearth on this stackexchange of example commands using ex, at least compared with the plethora of example commands using sed, awk and Perl. However, I myself have delved extensively into the POSIX specs for ex and I've been beating the drum for it ever since. I've written many answers using ex both here and on the vi/Vim stackexchange:

Further reading:

Another alternative is ex, the predecessor to vi. It is actually the POSIX tool of choice for in-place scripted file editing; it is extraordinarily more flexible than sed -i and arguably even more portable than Perl. (If you stay outside of the Windows world, it's unarguably more portable than Perl.)

There is a relative dearth on this stackexchange of example commands using ex, at least compared with the plethora of example commands using sed, awk and Perl. However, I myself have delved extensively into the POSIX specs for ex and I've been beating the drum for it ever since. I've written many answers using ex both here and on the vi/Vim stackexchange:

Further reading:

Another alternative is ex, the predecessor to vi. It is actually the POSIX tool of choice for in-place scripted file editing; it is extraordinarily more flexible than sed -i and arguably even more portable than Perl. (If you stay outside of the Windows world, it's unarguably more portable than Perl.)

There is a relative dearth on this stackexchange of example commands using ex, at least compared with the plethora of example commands using sed, awk and Perl. However, I myself have delved extensively into the POSIX specs for ex and I've been beating the drum for it ever since. I've written many answers using ex both here and on the vi/Vim stackexchange:

Further reading:

Source Link
Wildcard
  • 37.5k
  • 30
  • 149
  • 284

Another alternative is ex, the predecessor to vi. It is actually the POSIX tool of choice for in-place scripted file editing; it is extraordinarily more flexible than sed -i and arguably even more portable than Perl. (If you stay outside of the Windows world, it's unarguably more portable than Perl.)

There is a relative dearth on this stackexchange of example commands using ex, at least compared with the plethora of example commands using sed, awk and Perl. However, I myself have delved extensively into the POSIX specs for ex and I've been beating the drum for it ever since. I've written many answers using ex both here and on the vi/Vim stackexchange:

Further reading: