Quitting Vi
-
I was taught ZZ too, years ago, so that's what I use as well. Or q! if I'm not saving.
But I'm like @travisdh1 and prefer nano.
-
I use nano more than Vi.
I just don't like the blank interface for it. Now I understand at time vi is preferred do to word wrapping etc. And then I'll use Vi.
-
I prefer vi... I've been burned by not having nano in the past and forced myself to learn vi because of that.
-
@coliver said in Quitting Vi:
I prefer vi... I've been burned by not having nano in the past and forced myself to learn vi because of that.
Same here. I've seen Fortune 100 companies production brought down because no one knew vi and nothing else was available in a crash.
-
@scottalanmiller said in Quitting Vi:
@coliver said in Quitting Vi:
I prefer vi... I've been burned by not having nano in the past and forced myself to learn vi because of that.
Same here. I've seen Fortune 100 companies production brought down because no one knew vi and nothing else was available in a crash.
These scenarios are so out past the moon for most of us that they would rarely occur. Like buying 4 servers to protect from 2 of them dying.
Now this doesn't mean don't learn Vi (I try and learn myself) I just don't like the interface.
-
@dustinb3403 said in Quitting Vi:
@scottalanmiller said in Quitting Vi:
@coliver said in Quitting Vi:
I prefer vi... I've been burned by not having nano in the past and forced myself to learn vi because of that.
Same here. I've seen Fortune 100 companies production brought down because no one knew vi and nothing else was available in a crash.
These scenarios are so out past the moon for most of us that they would rarely occur. Like buying 4 servers to protect from 2 of them dying.
That's true... although it happened to me when working in an SMB (tiny 100-200 person SMB) with some legacy systems.
-
@dustinb3403 said in Quitting Vi:
@scottalanmiller said in Quitting Vi:
@coliver said in Quitting Vi:
I prefer vi... I've been burned by not having nano in the past and forced myself to learn vi because of that.
Same here. I've seen Fortune 100 companies production brought down because no one knew vi and nothing else was available in a crash.
These scenarios are so out past the moon for most of us that they would rarely occur. Like buying 4 servers to protect from 2 of them dying.
Not as crazy as you might think. All it takes is certain storage devices failing.
-
For those like me who doesn't know vi very well, a reference sheet.
http://www.lagmonster.org/docs/vi.html
If you do a quick Google search, you will find a number of reference cards and sheets for vi from colleges and universities.
-
I definitely prefer nano, but knowing vi (at least to a base degree like i do) is pretty much necessary as you are likely to eventually run into a situation where you don't have access to nano. Common discussion around here though
-
My daughter's first laptop that she got here recently was Korora 25. I then pointed her to this site https://vim-adventures.com/ and she learned VIM as a game. Her and I are going through a Python class together.
-
@penguinwrangler said in Quitting Vi:
My daughter's first laptop that she got here recently was Korora 25. I then pointed her to this site https://vim-adventures.com/ and she learned VIM as a game. Her and I are going through a Python class together.
What a great idea
-
@penguinwrangler said in Quitting Vi:
My daughter's first laptop that she got here recently was Korora 25. I then pointed her to this site https://vim-adventures.com/ and she learned VIM as a game. Her and I are going through a Python class together.
If you don't mind me asking, how old is your daughter? My 7-year-old got a NextBook with Windows 10 for christmas and I'm considering trying at least Fedora on it for her instead.
-
Vi is not hard. All you have to know at minimum is how to get in it, how to move the curser & change/add text, how to save, and how to exit:
vi
up/down/left/right
ZZ
q!If you can remember that, you'll be just fine.
-
@tim_g said in Quitting Vi:
Vi is not hard. All you have to know at minimum is how to get in it, how to move the curser & change/add text, how to save, and how to exit:
vi
up/down/left/right
ZZ
q!If you can remember that, you'll be just fine.
ZZ is a new one for me I just use :wq.
-
@coliver said in Quitting Vi:
@tim_g said in Quitting Vi:
Vi is not hard. All you have to know at minimum is how to get in it, how to move the curser & change/add text, how to save, and how to exit:
vi
up/down/left/right
ZZ
q!If you can remember that, you'll be just fine.
ZZ is a new one for me I just use :wq.
Same
-
Dont forget about i. I always do.
-
@tim_g said in Quitting Vi:
Vi is not hard. All you have to know at minimum is how to get in it, how to move the curser & change/add text, how to save, and how to exit:
vi
up/down/left/right
ZZ
q!If you can remember that, you'll be just fine.
You should add
/to your list. -
@dustinb3403 said in Quitting Vi:
@scottalanmiller said in Quitting Vi:
@coliver said in Quitting Vi:
I prefer vi... I've been burned by not having nano in the past and forced myself to learn vi because of that.
Same here. I've seen Fortune 100 companies production brought down because no one knew vi and nothing else was available in a crash.
These scenarios are so out past the moon for most of us that they would rarely occur. Like buying 4 servers to protect from 2 of them dying.
Now this doesn't mean don't learn Vi (I try and learn myself) I just don't like the interface.
We have over 1000 Linux servers and Vi is the only option on the greater majority (75%+). None of our QA, Stage, or Production systems come with anything else.
I like and use Vim, and go with Vi if that's all I've got. Here's a great book for anyone looking to become a Vim power user: Practical Vim (https://pragprog.com/book/dnvim2/practical-vim-second-edition)
-
Also, installing Vim and typing 'vimtutor' at any terminal will launch an interactive beginner's tutorial on Vim.
-
i'm going to drown in linux-related books
