>>22082 Nice. I don't use ed that much tbh, but I went through the GNU ed manual a while back, to learn the commands for use with vim since a lot of them are similar. The g command is great for a lot of things. Like if you're editing C code, you can use something like g/^{/-n to list all function declarations and structs in a file (assuming all the braces are on the line directly after the function declaration). Using rlwrap together with ed to get command history is pretty useful too.

>>22100 I use ed to edit most config files. Sure, I do have Emacs installed and I can use it to edit remote files too, but when you know you just need to change that specific word on that specific line using ed is faster than even vim. And even if you don't know where it is, g/<re>/n followed by <line>s/<needle>/<sub>/n is just as quick and easy. ?

>>22107 yeah ed is perfect for those quick edits

>>22082 also if you have source-highlight installed you can actually pipe it through that for some basic syntax highlighting which is neat

>>22177 I use it to write full files too. It takes a bit to master the write-edit errors-write cycle but it's really not any less efficient than using vim. >>22179 While I do have it on other editors, syntax highlighting is massively overrated and things like tree-sitter are solutions to a problem that should not exist in the first place.

how to learn ed