3 ms·
Next step: programming using ed. But jokes aside, use whatever environment you like best. For me syntax highlighting is extremely useful. Knowing whether some
by adrianN 11y ago
Next step: programming using ed.
But jokes aside, use whatever environment you like best. For me syntax highlighting is extremely useful. Knowing whether some strings of characters is a type or a variable, or a class type or a basic type makes programming just that much easier. It also helps catching simple typos if something doesn't have the color you'd expect.
- marcosdumay 11y agoWell, not ed, but refactoring Haskell code with sed incredibly nice.
- onion2k 11y agoI find syntax highlighting is brilliant for focusing on small elements in code. Switching it off is useful for looking at the overall structure of a closure.
- gkya 11y agoEd is fun. I admit that it's mere geekery to prefer it over something feasible, but it's worth it when you spend an afternoon just playing with it. Also I guess it'd be nice exercise for vi users. But some syntax highlighting is really useful nearly universally.
- SixSigma 11y agoA high number of Unix programmers (Ken Thompson, Brian Kernighan, Doug McIlroy, Tom Duff & Bjarne Stroustrup) used sam at Bell Labs, which is known as "ed on steroids, lots of steroids". http://sam.cat-v.org/ http://sam.cat-v.org/
- mavelikara 11y agoFrom an interview with Peter Salus [1]: By the way, 'em' stands for 'editor for mortals' - I christened it that after Ken Thompson visited our lab at QMC while I was developing it and said something like: "yeah, I've seen editors like that, but I don't feel a need for them, I don't want to see the state of the file when I'm editing". [1]: http://web.archive.org/web/20080103071208/http://www.dcs.qmul.ac.uk/~george/history/ http://web.archive.org/web/20080103071208/http://www.dcs.qmu...
- watchdogtimer 11y agoA step up from ed but a step below vim is nvi. I've always preferred nvi over vim because: 1) there's no lag when I scroll up or down through a file line-by-line, 2) it shows a list of matching files by default when using tab completion in command mode (same as bash), vs picking the first matching filename, and 3) it uses fewer resources when you screw up (http://galexander.org/vim_sucks.html http://galexander.org/vim_sucks.html) I used to think that the lack of syntax highlighting was its biggest weakness, but now that's apparently a virtue :-) .
- majewsky 11y agoRe 2) set wildmode=list:longest EDIT: Re 3), there's something weird going on. I just tried the benchmark from the article that you linked ("1000000aaeou<ESC>"), and it really did not complete in a useful timeframe. However, when I insert the text once, yank it, then paste it with repeat ("iaeou<ESC>^y4l1000000p"), the operation completes instantly, and I can still browse the file without any slowdown. Undo/redo across this operation seems to take some seconds, though.
- watchdogtimer 11y agoThanks for the list hint!