Vim for Editing Files in Linux

Info

Level: Beginner
Presenter: Eli the Computer Guy
Date Created: September 14, 2010
Length of Class: 35 Minutes
Tracks

Linux
Prerequisites

Introduction to Linux
Installing Linux
Basic Linux Tasks
Purpose of Class

This class teaches students how to edit configuration files in Linux using the text editor VIM.
Topics Covered

Starting VIM
Editing Files
Searching in Files
Opening, Saving and Exiting Files
Class Notes

Introduction
No .txt -- no file association
Starting VIM
Sudo vim XXX (opens a file, or creates file)
Sudo -- sometimes you need, sometimes not... if you use it it will always work...
To change ownership of a file (Sometimes needed to edit .ini and configuration files)- Sudo chown user file
Editing and Navigating
a = insert, esc = exit insert
:/ = find (use wildcards)
:/? = Find backward
n = next
Exiting and Saving
:q = quit
:q! = quit no save
:wq = save and quit
:e = open file
:w = save as
Final Thoughts...
Very complicated... Lots of options... these are good enough to start with....
Resources

Vim Website: http://www.vim.org/
Vim Manual: http://vimdoc.sourceforge.net/vimum.html

• Category

  Science & Technology

[Cleber Jose de Rossi]

I prefer VI, I think it is easier!But VIM has more features.

[elithecomputerguy]

I've found it's really a personal preference type of thing. I learned VIM first and liked it so that's what I use... VI is good too...

[rasix86]

Holy crap.. some seriously bad suggestions in the 1st 10 minutes already... open all files as sudo? you cant be serious. and even worse: change ownership of files? this can in worst case break your system....

[Paul Pavalone]

I've been having an overheating problem with my Ubuntu...i.e. the computer shuts down when it hits it's critical trip point of 106 degrees. I've changed the permissions and ownership of the files correctly but I am still unable to modify or delete the thermal zone trip point files...Any suggestions? And no, I am not concerned about burning out my cpu.

[Deshinffxi]

True but as he said right at the beginning: you won't know what the ownership is until after you've done any edits and want to save the file. It's better to just get used to writing "sudo vim" than "vim" and realising after a massive edit "oh I don't have permission"

You don't NEED to do it but it's erring on the side of caution

[rasix86]

I wonder what all those admins out there, that dont have sudo installed, do in such cases... seriously, that statement is plain wrong

[ideasman42]

If your editing config files as an admin, you very well may have to use sudo, I think he just misses context while explaining.

[Vincent Vetsch]

Use sudo or su sparingly. Use it based on the file ownership.

[TheKarabouzouklis]

he said you can't edit all files if you don't use sudo which is true

[Ricardo Band]

These videos aren't great. He teaches wrong and very insecure things. People shouldn't listen to him and he should stop doing this crap or try learning how things are right before telling wrong stuff.

[Ricardo Band]

5:20 Always use sudo? Hell, no!

6:35 Case by case? What about file permissions?

8:35 Change ownerchip of files? He can't be serious?

9:45 Don't learn security? Sure, it's better to learn everything wrong and then right again..

10:40 123456 is not a good password.

20:15 Stupidly long configuration files? Long is good, more options, more examples and documentation.

33:45 Why does he talk bad about linux all the time?

35:05 Word for making books? Never heard of some called LaTeX?

Eli you suck.

[nbensa]

6:23 WHAT? Did you say "you CAN'T run vim without sudo"?? Enough, I was going to watch the whole video, but this is a blatant bullshit. You're spreading lies. You better stop teaching because you are doing it WRONG.