The Lounge is rated PG. If you're about to post something you wouldn't want your
kid sister to read then don't post it. No flame wars, no abusive conduct, no programming
questions and please don't post ads.
So my dad had a "sharp" PC in the eigthies. It didn't have a HD yet and you boothed by locking a 5.25" floppy disk in to drive A. You could use another floppy on drive B to work on.
This thing had a text editor where you had to move the cursor by pressing ctrl and a key combination. This was for moving up and down, put in edit mode, remove letters, words or lines etc ...
And today I accidently ran into VIM .
I knew this still exists and it is still used BY DEFAULT on linux systems. But really, nothing better than VIM? So I was looking into using nano instead and on the internet people seem to actually PREFER vim! Anyways, I was very happy to edit my crontab in nano instead.
I've never used vim, but I started out coding in vi.
At first, it was horrible to use and utterly counter-intuitive. For example, "L" moves right, for crying out loud! It made me wonder just how much acid Kernighan, Richie and co. were doing back in the day.
After a couple of months, though, as I got more familiar with it and learned more about combining it with the magic of "ex" I started thinking "this is actually pretty cool". After a couple of years, I was absolutely, head-over-heels in love with it.
By the time I'd drifted into Windows development, I found myself pining for vi on a daily basis. It was the best damned text editor that I could imagine and nothing would ever come close to the old magic. I missed it like crazy for a good few years.
Nowadays, as it so often is with former lovers, I really can't imagine ever going back there.
The first proper editor we used in our development team was MultiEdit which at the time was miraculous. One of my colleagues, who worked on Unix systems as well as DOS systems, asked me if there was a version for Unix as he found it a pain switching between MultiEdit and Vi. I told him I couldn't get him Multiedit for Unix, but could get him Vi for DOS! He nearly punched me.
I'm an optoholic - my glass is always half full of vodka.
I moved out of Unix and into ms quite early, so edlin was my most used text-editor/programming IDE (heh).
When I found that it was still included in XP, I just had to have a go, for a few days. It didn't take long for (most of) the finger-bending commands to come back, but it was so slow and arduous to work with!
I've paid for god-only knows how many TextPad licenses, and I always have NPP installed alongside it (better encoding support), and there's no way in the world I would wish to go back to "the old ways".
And anyone who'd give up intellisense must be out of his mind.
I wanna be a eunuchs developer! Pass me a bread knife!
".45 ACP - because shooting twice is just silly" - JSOP, 2010 - You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010 - When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
It is well made, it has its philosophy. Once you get along with that you can become productive because of the quality of realization.
There has been a time where my X window wouldn't work and I had to spend a lot of time trying installations and configurations. No network so I was stuck with CD 1, 2 and 3 of the various installations, bought along the magazines. Choices were EMACS and VIM... IMHO EMACS has a nice screen format, comfortable for an old user of MSDOS 5 edit but the commands are far too convoluted. With Vim basic operativity is faster to get, always IMHO.
I started out with TECO on a PDP-11, very similar I suspect.
But for most of my work with OpenVMS I used -- and still use -- EDT, which is still a very simple editor. I have several macros defined that help me do things.
All proper editors have a line mode.