Do you use vim in its not-vi mode? (It's one of those days, I can't talk right. )
It's actually also a very good text editor alternative if you're on Windows.
It's actually also a very good text editor alternative if you're on Windows.
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
Yep, vim is what I actually use, but it's called with vi and I call it vi. Nearly 30 years of habit is hard to break!There are other text editors...
Vim FTW
There are several ways, including what EM mentioned, but I'm too lazy for that many keystrokes, so I always use one, x, to save and exit.And I hate Vi. I can't never figure out how to save a modified file.
Proud, primitive vi user here! :laugh:Vi is considered primitive as are its users
Heresy.x - to write/save the file and exit
Proud, primitive vi user here! :laugh:
Seriously, though, considering its power, it's kind of funny that it's considered primitive. And once you know its commands and functions, it's as natural as breathing.
We could substitute DOS's edlin for ed. :idea: When it comes to primitive, that would be a good start! :laugh:It's possible to use a tty buffer display model put together with ed and get something more primitive but I don't think it'll be easy. :rofl:
We could substitute DOS's edlin for ed. :idea: When it comes to primitive, that would be a good start! :laugh:
My guess is that it's still there purely for historical integrity and, perhaps, backward compatibility. There may still be scripts hanging around that call it...although you have to wonder about a system that hasn't been touched in THAT long.I know ed is standard in just about all *nix systems, since 1971 I believe. But would anyone actually still use it? - apart from absolute hard core types possibly.
No kidding.To quote the Wiki...
Famous for its terseness, ed gives almost no visual feedback. For example, the message that ed will produce in case of error, or when it wants to make sure the user wishes to quit without saving, is "?". It does not report the current filename or line number, or even display the results of a change to the text, unless requested. This terseness was appropriate in the early versions of Unix, when consoles were teletypes, modems were slow, and memory was precious.
awesome stuff...
That's the thing--it's really powerful. Oh, it definitely can seem daunting (and cryptic and any number of other things) and like the learning curve is ridiculous, but if you start with a few basics and get them down pat, and then add bit by bit to your repertoire, before you know it you're using vi like an old hand.I started to really get into vi/vim a few months back, ran through the vim-tutor a few times and was getting the hang of it... then I stopped using it and forgot half of it.
But, for a moment, I could do some kinda cool things easily.
Using Slackware was my intro to Vi also. It was one of the few distros that I tried at the time that didn't come with nano by default. That's where I left it also.I hated vi and ed with a passion, but there were time when I had to use 'em; particularly when I was using Slackware.
Yeah, I really want to get back into it. I think I actually posted the coolest thing I learned in this thread a few months ago... it was using a macro to increment a number or alpha character. But it was weird, I had a success rate of about 80% with it.That's the thing--it's really powerful. Oh, it definitely can seem daunting (and cryptic and any number of other things) and like the learning curve is ridiculous, but if you start with a few basics and get them down pat, and then add bit by bit to your repertoire, before you know it you're using vi like an old hand.
+1 for kwrite. That's my editor of choice when doing GUI.For gui editor I like gedit and kwrite.
I use that, too, but it is too large and unwieldy (and takes too long to load) for fixing small files.
Agree, I just felt like plugging it.