Quitting Vi
-
@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
-
@ramblingbiped said in Quitting Vi:
@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)
At that point, why do you even need to touch any individual server rather than using your management platform of choice (salt, tower, etc.)
-
@travisdh1 said in Quitting Vi:
@ramblingbiped said in Quitting Vi:
@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)
At that point, why do you even need to touch any individual server rather than using your management platform of choice (salt, tower, etc.)
We don't normally unless we have to investigate any issues that might arise. And even then we don't normally need a text editor.
-
@travisdh1 said in Quitting Vi:
@ramblingbiped said in Quitting Vi:
@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)
At that point, why do you even need to touch any individual server rather than using your management platform of choice (salt, tower, etc.)
Wow... yeah there's no way I would be doing anything on individual servers... like ever. Unless 999 of them are the same and 1 was unique in such as way it wouldn't make sense to use a configuration management tool. (puppet/chef/ansible/salt/etc.)
-
The way I learned was to use :q!
I always use that, and if I want to say while still working I use :w! -
@jmoore said in Quitting Vi:
Probably a silly question here. I see people quitting Vi using :x and :wq if I remember right. I've always just used the :x option to save my work. Am I using this correctly or should I be doing it another way?
:xfor the win
-
@eddiejennings said in Quitting Vi:
@jmoore said in Quitting Vi:
Probably a silly question here. I see people quitting Vi using :x and :wq if I remember right. I've always just used the :x option to save my work. Am I using this correctly or should I be doing it another way?
:xfor the winZZ is faster.
-
@scottalanmiller I'll try it the next time I'm in vi.
