0:00 - Introduction 0:53 - edit a file in vim (vim filename.txt || vi filename.txt) 1:12 - how to quit vim (:q) 1:50 - saving files in vim, and other ways of exiting 2:12 - what are vim modes (ESC/i) 3:14 - how to delete a single line with vim (dd) 3:30 - how to delete multiple lines with vim (#dd, e.g. 5dd) 3:47 - how to undo changes in vim (u) 4:06 - how to 'redo' changes (ctrl-r) 4:32 - searching text in vim ( /yourtext + ENTER) 5:52 - how to find and replace text in vim ( :%s/yourtext/replacetext/g (+c)) 7:23 - Conclusion
Thanks, I *really* wanted to get those in there but was already over my original goal of 5 minutes. I figured copy/paste can still be done with the normal readline shortcuts that people are used to from working in the shell, but the vim commands you mention are better. Cheers!
Actually I think this is overtly the wrong way to teach vi. It's almost always taught like this and it's the reason why so many people are confused about and hate vi. The tutorial *does* give you the basics you need to get in, edit text, and exit. However... if you see vi as a long list of random commands it will fundamentally be frustrating, make no sense, and be hard to remember let alone advance your skills. Rather, by putting an emphasis on the easy to remember fundamental movement primitives and how they can be chained together to form the "vi language" is critical to understanding why vi is so elegant, rather than leaving people wondering why an editor would be modal in the first place. If a beginner tutorial doesn't demonstrate how you can combine primatives into something like ciw (change inner word) or ci" (change inner quotes) and then repeat it on a totally different word with period... then honestly many people just won't get it, and continue to see vim as some kind of relic of the distant past rather than the elegant tool that it is.
D'OH -- I *knew* I would get something simple like this wrong. That's what I get for being an emacs user :-D. Thanks so much for pointing this out. Cheers!
_pressing colon in normal mode_ Launches unguided floaters. _pressing colon in command mode_ Launches guided floaters. I need to stop watching these videos that make no sense to me and then making $hitty puns..
Great! Vim was recommended to me yesterday by the lead developer where I work. (I am not currently employed as a developer, I just befriended this gentleman.) I currently alternate between two of the most popular text editors in my studies, and I will be beginning my studies in a coding boot camp 2 days from now. I am convinced that this will be a valuable tool in my developer's tool box, and your simple
you goota be one of the most professional youtube teachers I-ve ever seen. even the videos timeline has the codes to assist. this is gold man, definately spreading the word!
I first used vi in the early 90's it is one of those tools you either use all the time or you forget all the shortcuts, so thanks for the refresher. One thing you missed is: set nonumber. Always handy to know how to unset something you showed how to set. All the best!
you've done a great tutorial! Clear, concise explanation but you've also struck the balance between being useful and getting overwhelming. Keep up the good work!
cut from current line to specified: d G replace word from current position cw replace entire word: ciw Replace line from current position: C my most appreciated commands
I've seen this video a couple of months ago and ended up falling back to nano, but I'm once again trying to use this as my main terminal editor, and I gotta say I really enjoy it, thank you for making such a consive video, that's what makes the linux community go forward.
Omg thank you so much just started my Operating systems course and had no idea what vim was this was an amazing introduction really appreciate the simplicity of it!
Another basics that I recommend: :! - send command to terminal (useful for git stuff and some basic commands, not recommended for interactive commands) :e - open the netrw file navigator inside vim (you can simply type ":e ." to use it on the current directory) :tabnew - create a new tab :tabedit - opens a new tab editing a specific file (or you can type ":tabedit ." to use netrw for interective file selection) g, t - switch to the right tab g, T - switch to the left tab Some tricks with split: CTRL + w, arrow (up/down/left/right) - split navigation (when you use :term, NERDTree and another split stuff inside vim, similar to tmux) :term - opens a shell inside vim (neovim and most recent versions of vim, work as a split) CTRL + w, s - create a vertical split (or you can type ":vsp" on normal mode) CTRL + w, v - create a horizontal split (or you can type ":sp" on normal mode) And some of my favorite extensions: :Files - opens a fzf navigation through the current directory (useful for large projects) :VirtualEnvActivate - forces vim to use Python from a specific virtualenv (I've tested it with virtualenvwrapper, maybe works with venv too) :VirtualEnvList - list all virtualenvs :VirtualEnvDeactivate - switch back to the default Python from OS For the :Files you need fzf and fzf.vim (both from junegunn on GitHub), and for the VirtualEnv commands you need vim-virtualenv (from jmcantrell on GitHub).
Glad that you got something out of it! And it's a miracle that I cut this video down to 8 minutes. Most of my videos promise 8 minutes and end up actually being 30, because I get extremely excited about whatever I'm talking about and lose track of time :-D.
@@tutoriaLinux Glad that you cut it down to 8 minutes. I was looking for something simple to learn basic editing. 1 week of starting with Vim and I can go by without touching the mouse. I am still very slow, but I will get there. Thanks.
Have you guys heard about micro? It's a terminal code editor designed to be one step above nano. It has modern shortcuts, full mouse support and syntax highlighting.
Your channel is the most useful source of tips and tricks for me. Without 'My 90 reasons to not use Windows' and 'Why we should burn systemd to the ground' stuff. I very much appreciate it.
wow, I found this video to be exactly the type of quick and dirty explanation I needed. I hope you have more videos just like this for EVERYTHING. I subbed and will rifle through your videos now. Great Vid, seriously
A great way to teach people vim is to have them install the vscode plugin. Then teach them things like the built in find and replace can be replaced by %s/foo/bar/g etc. Super nice
@@chezchezchezchez If you install neovim, and use the neovim extension. It basically has full neovim functionality whilst also including inbuilt vscode functionality. Very nice
@6:34 the 'g' stands for "global". Greedy is a term that's usually used to describe regular expressions that look for as many matches as possible. They have similar definitions, but are used differently when describing those specific use cases. Hope this helps. :)
Good quick overview, thanks. I used vi for 20 years. Now after a long period of not programming, I'm getting back into it. I hope the memory is still retained in my fingertips. BTW, g means "global" not "greedy"
Thanks. I'm pretty damn new to all of this and had avoided vim as there seemed to be two camps, those that used editors like nano and avoided vim like Covid-19 and those that gave you the feeling that any GUI was heresy. You explained it easily, almost casually and didn't make it appear daunting at all
holy moly, as a person that’s used non-terminal apps ‘n fat IDEs, this was refreshing! thanks for this. i personally always thought it was some ancient thing with wonky commands... it seem i was thinking of emacs...
Some tips I learned from working on remote servers with really unreliable connections, dialing into Unix, Solaris and the not-so-usual server kind: - you'll find vi in pretty much ANY *nix system, doesn't matter how old, small it can be, vi, will most likely be there, so LEARN IT, some day in the fallout future you might have to work on a terminal from 1982 - You can press ESC as many times as you want, very good if you have significant input lag and you're not sure where you're standing. - "hjkl" replaces arrow keys. Useful when you're not sure if all the keyboard signals are being sent/received with different communication protocols. - 0 takes you to the first character of the line, $ to the last - w takes you one word forward, b one back - There's shells like "ksh" that leverage vi in the command line We could go all day ! :)
That's too funny! ...stick a noob in front of a keyboard and get him to quit vi... Hey, that was me! Based on that alone (I'm still going through your video, only at 1:52 on the timer as of this comment) I'm commenting and subscribing.
I found vim difficult so use nano. But your easy explanation will make me to try vim again. It is much easier than I thought. Thanks for the clear explanation.
I cant believe this video is upto 8mins, it seemed more like 2mins as it was really interesting to watch, I naturally like the simplicity of nano but because of you, I am gonna quit using nano and switch to vim. you should definitely make a part two. Also, that joke about sticking a noob into a terminal running vim and them not being able to quit is soo true, faced it many times 🤣😂
Can learning VIM well allow me to replace all other editors - even markdown editors and maybe even LibreOffice? Can it use images? I use markdown a lot (efficient as heck). I am learning nano now as I hope to have a server and may need to access it remotely on rare occasion. I am also trying out gedit (so easy!) and micro, but am not convinced that micro can be accessed remotely (for a noob, at least) and I know gedit cannot (I use Debian, not Ubuntu).
Colon then (q) to quit. This is exactly what I came here to learn. Leaving now! P.s.: In remote server when you do not have Sublume and Atom, Vim is not the only choice, there is always Pico and Nano.
This was actually a very helpful explanation, just what I was looking for! Great job. I have used LInux (dabbled with Ubuntu, Debian, Debian derived distributions, Fedora, ...) and some Bash shell command line commands - the famous powerful Linux emulator tool: THE THERMINAL! /dreaded by people who are only used with GUI's , beloved by powerusers -- since about 6 years ago, but I have also spend a lot of time on OS X as I dualbooted it with Linux, in which longer time period I dabbled a lot less with Linux and the command line. I'm not a programmer, developer, system administrator whatsoever, I don't know any programming language. (had a few python lessons which I was terrible at, score of 1/4 for a project - which I 'kind of' copied huge parts from a friend -: programming an hourglass with a visual presentation and so dreaded it pretty terribly) But I find open-source software, the Linux and GNU philosophies, the forms of freedom you can find in it, to be pretty enchanting; so finally getting a first grasp on one of the, if not most, widely used CLI text editors across the Unix and Unix-like landscapes is pretty cool. A computer that just works for desktop applications is very understandable, not everybody wants to thinker, break, fix, find, source, compile, fail & try again; with their computer. But it has a uniqueness to it. I've always prefered Unix & the like systems some way above Windows, even though the Linux & Unix desktops are 'scattered', if you know what I'm trying to say. Yes, I'm talking about desktop experiences/little experiments, not server and other applications.
i am using a remote server on putty on mac and I am trying to copy a c code in the vim but i am not able to, I have tried everything. the code is in my mac and I want to copy the code into the file which I have created in the remote server using vim. how do I do that.
Awesome but what if I accidentally hit wq a whole bunch of times and forgot to add the : first? It didnt change anything except move the cursor a couple of times and would say recording. Classic rookie mistake but I dont think I messed up my config. Thoughts?
One thing thats rarely mentioned on Vim videos is the need to be a touch-typer. i.e you should be able to type text with all fingers without looking at the keyboard. If you're a two finger typer, you will be missing out on 80% of what Vim is about. Seriously, Touch-Typing is a pre-requisite for successfully and fully using Vim. ...that and remapping your Caps Lock key to function as Esc.
0:00 - Introduction
0:53 - edit a file in vim (vim filename.txt || vi filename.txt)
1:12 - how to quit vim (:q)
1:50 - saving files in vim, and other ways of exiting
2:12 - what are vim modes (ESC/i)
3:14 - how to delete a single line with vim (dd)
3:30 - how to delete multiple lines with vim (#dd, e.g. 5dd)
3:47 - how to undo changes in vim (u)
4:06 - how to 'redo' changes (ctrl-r)
4:32 - searching text in vim ( /yourtext + ENTER)
5:52 - how to find and replace text in vim ( :%s/yourtext/replacetext/g (+c))
7:23 - Conclusion
tutoriaLinux where is the nano video?
Thank you for an excellent introduction to Vim. This text editor is amazing in many ways.
@@averagejeffs Nano's the best =D
Emacs
I loved that joke of a noob and terminal. LMAO! 😂😆
That joke about putting a noob in vim editor is seriously underrated. I remember my first time trying to exit it xD
I'm going thru it right now!! facepalm!
@@shazib25 me too 😢
That is why I am watching this tutorial! Haha LOL.
If everyone does it to the point of it being a meme it's not a noob foible, it's unintuitive design choices.
@@ragnarok7976 I hear people ramble all the time about how awesome vim is, and I still don't understand why. "Unintuitive" is putting it mildly.
Surprised you didn't mention
yy to copy a line
p to paste
I work with vim every single day, and I use these 1000 times a day.
Thanks, I *really* wanted to get those in there but was already over my original goal of 5 minutes. I figured copy/paste can still be done with the normal readline shortcuts that people are used to from working in the shell, but the vim commands you mention are better. Cheers!
Neat! Also nice is d commands like dd copy what they deleted, so you can use 3dd, move, and p to move 3 lines!
lower case p to paste after, capital P (shift+p) to paste before. ;)
or . to call the last command
As a full-time vim user of many years - I think this is a great intro. Enough to be useful, and possibly intrigue people to learn more. :-)
Actually I think this is overtly the wrong way to teach vi. It's almost always taught like this and it's the reason why so many people are confused about and hate vi. The tutorial *does* give you the basics you need to get in, edit text, and exit. However... if you see vi as a long list of random commands it will fundamentally be frustrating, make no sense, and be hard to remember let alone advance your skills. Rather, by putting an emphasis on the easy to remember fundamental movement primitives and how they can be chained together to form the "vi language" is critical to understanding why vi is so elegant, rather than leaving people wondering why an editor would be modal in the first place. If a beginner tutorial doesn't demonstrate how you can combine primatives into something like ciw (change inner word) or ci" (change inner quotes) and then repeat it on a totally different word with period... then honestly many people just won't get it, and continue to see vim as some kind of relic of the distant past rather than the elegant tool that it is.
@@entelinare there any resources like this you would recommend?
@@ironicCryptidI know I'm late, but I highly recommend ThePrimeagen's video tutorials
I've learned a lot just by reading the comments! That's power of the community! :D
Shortest 8 mins of my life, you just hooked me man!! You're great teacher.
it really didn't feel like that many minutes, for sure!
What you call "command mode" is "normal mode". Command mode is entered by pressing colon in normal mode
D'OH -- I *knew* I would get something simple like this wrong. That's what I get for being an emacs user :-D. Thanks so much for pointing this out. Cheers!
@@tutoriaLinux :%s/command mode/normal mode/g
@@juandonosa374 Dude , I'm so happy I get this joke. Thanks for boosting my morale.
_pressing colon in normal mode_
Launches unguided floaters.
_pressing colon in command mode_
Launches guided floaters.
I need to stop watching these videos that make no sense to me and then making $hitty puns..
@@juandonosa374 I don't think that works right ?
This is actually the only video i've watched about vim that actually make me interested in learning vim. Thank you.
a lot of the tutorials are at least 25 minutes long, kinda imtimidating
exactly, me too
Many Vim tutorials are just guys flexing their Vim skills while pretending to help.
Thank you for that finally real Vim Basics video. Keep up.
Great! Vim was recommended to me yesterday by the lead developer where I work. (I am not currently employed as a developer, I just befriended this gentleman.) I currently alternate between two of the most popular text editors in my studies, and I will be beginning my studies in a coding boot camp 2 days from now. I am convinced that this will be a valuable tool in my developer's tool box, and your simple
its my first time diving into arch. i feel like i am manipulating individual atoms. thanks
well done, I'm about 4 months into my arch journey too and so far so good. In fact better than that, Arch is awesome.
Lol
Gentoo baby
You can use nano in arch, it's easier
That was the perfect amount of knowledge for a novice like me to get started. You sir, know what you're doing. Thank you.
you goota be one of the most professional youtube teachers I-ve ever seen. even the videos timeline has the codes to assist. this is gold man, definately spreading the word!
I first used vi in the early 90's it is one of those tools you either use all the time or you forget all the shortcuts, so thanks for the refresher.
One thing you missed is: set nonumber.
Always handy to know how to unset something you showed how to set.
All the best!
My friend told me he'll pay me if I manage to learn Vim.
I've never earned so much for watching a 9-minute video. Thanks :D
Getting paid to learn vim is the best thing I have ever heard of. You're truly living your best life.
Insanely useful. I'm in over my head, but now I have an ear above water
you've done a great tutorial! Clear, concise explanation but you've also struck the balance between being useful and getting overwhelming. Keep up the good work!
Small correction: The g-flag on your search-and-replace command stands for "global"
"greedy" means something different in regex terms
i had the same thought
cut from current line to specified:
d G
replace word from current position
cw
replace entire word:
ciw
Replace line from current position:
C
my most appreciated commands
Super useful, thanks!
El mejor tutorial que he visto sobre Vim (Vi) en TH-cam. Increíble. Gracias.
I've been using Vim as my main editor in Linux environments for about 6 months now. Just learned dd and %s/find/replace/g(c). Thanks man!
I've seen this video a couple of months ago and ended up falling back to nano, but I'm once again trying to use this as my main terminal editor, and I gotta say I really enjoy it, thank you for making such a consive video, that's what makes the linux community go forward.
my internship is literally scripting in the command line. This video is a lifesaver.
Thank you for making the Vim basics very very easy. I learnt a lot in few minutes.
Omg thank you so much just started my Operating systems course and had no idea what vim was this was an amazing introduction really appreciate the simplicity of it!
Another basics that I recommend:
:! - send command to terminal (useful for git stuff and some basic commands, not recommended for interactive commands)
:e - open the netrw file navigator inside vim (you can simply type ":e ." to use it on the current directory)
:tabnew - create a new tab
:tabedit - opens a new tab editing a specific file (or you can type ":tabedit ." to use netrw for interective file selection)
g, t - switch to the right tab
g, T - switch to the left tab
Some tricks with split:
CTRL + w, arrow (up/down/left/right) - split navigation (when you use :term, NERDTree and another split stuff inside vim, similar to tmux)
:term - opens a shell inside vim (neovim and most recent versions of vim, work as a split)
CTRL + w, s - create a vertical split (or you can type ":vsp" on normal mode)
CTRL + w, v - create a horizontal split (or you can type ":sp" on normal mode)
And some of my favorite extensions:
:Files - opens a fzf navigation through the current directory (useful for large projects)
:VirtualEnvActivate - forces vim to use Python from a specific virtualenv (I've tested it with virtualenvwrapper, maybe works with venv too)
:VirtualEnvList - list all virtualenvs
:VirtualEnvDeactivate - switch back to the default Python from OS
For the :Files you need fzf and fzf.vim (both from junegunn on GitHub), and for the VirtualEnv commands you need vim-virtualenv (from jmcantrell on GitHub).
Just what I'm looking for. Looks like the only video on TH-cam on the topic. Kudos
Excellent tutorial. 8 minutes with a hefty ROI. Trying to get my Terraform cert - too much to learn, too little time...
Thanks David!
finally exited vim after several years, thank you!
Oh god bless you sir! I've been stuck in Vi for a year and a half :(
"Just keep hitting you"
Yeah, each time I need to use Vim, I keep hitting myself...
Thanks for getting me started in 8 minutes. Actually 30 minutes. Had to re-watch many parts of it. Thanks a lot.
Glad that you got something out of it! And it's a miracle that I cut this video down to 8 minutes. Most of my videos promise 8 minutes and end up actually being 30, because I get extremely excited about whatever I'm talking about and lose track of time :-D.
@@tutoriaLinux Glad that you cut it down to 8 minutes. I was looking for something simple to learn basic editing. 1 week of starting with Vim and I can go by without touching the mouse. I am still very slow, but I will get there. Thanks.
This was amazing. I was in a CentOS server and had to muck around and edit few files, this video saved my life! Thanks a lot!!!
Almost covering basics commands that you see in File and Edit menus of notepad or any other basic editor. Awesome starter!
As a newb vim user, I found the undo/redo commands and especially the search and replace function extremely helpful. Looking forward to the next one!
I was stuck in vi insert mode for 20 minutes during solo practice class, thanks for your help!
I used nano for a while now, and I think it's time to move to vim. Thanks!
Johnny you only need nano or pico
That's true, but I wanna learn something new and more advansed
Type vimtutor in terminal it would help you.
Have you guys heard about micro? It's a terminal code editor designed to be one step above nano. It has modern shortcuts, full mouse support and syntax highlighting.
@@nicolareiman9687 Thanks for this information. I've already found the humor of nerd in that tutor file.
rewatched this whenever I forgot something -amazing video!!!!! super organized!!!
thank you for the no-music intro
what is wrong if there is a music intro i am just asking ?? wanna know more about that if you will !
This was very helpful. Saved me an hour of frustration for sure. Thanks!
Your channel is the most useful source of tips and tricks for me. Without 'My 90 reasons to not use Windows' and 'Why we should burn systemd to the ground' stuff. I very much appreciate it.
wow, I found this video to be exactly the type of quick and dirty explanation I needed. I hope you have more videos just like this for EVERYTHING. I subbed and will rifle through your videos now. Great Vid, seriously
much needed video while I am learning docker. thanks man (cried when I hit ctrl+z each time instead of ctrl +r)
A great way to teach people vim is to have them install the vscode plugin. Then teach them things like the built in find and replace can be replaced by %s/foo/bar/g etc. Super nice
Timmy What about the visual studio plug-in? Is that equally good?
@@chezchezchezchez If you install neovim, and use the neovim extension. It basically has full neovim functionality whilst also including inbuilt vscode functionality. Very nice
@@Faunarr Thanks, how about Xcode? I'm now all Xcode.
Thanks!
@6:34 the 'g' stands for "global". Greedy is a term that's usually used to describe regular expressions that look for as many matches as possible. They have similar definitions, but are used differently when describing those specific use cases. Hope this helps. :)
The big one is :help (what you want to know here without brackets), I found out how to quit as a noob with this trick!
Great explanation. I remember pretty much every command you told.
Good quick overview, thanks. I used vi for 20 years. Now after a long period of not programming, I'm getting back into it. I hope the memory is still retained in my fingertips. BTW, g means "global" not "greedy"
yeah i recall that now, read that. thanks
Feeling great and comfortable after refreshing basic skills from your videos. god bless you !
I love these tutorials I'm currently in a cybersecurity course in high school and it's really helpful to watch your videos and take notes :)
Great tutorial man.Before I found this tutorial I think that vim made for only advanced programmers.But now i think it's make your life lot easier
Thanks. I'm pretty damn new to all of this and had avoided vim as there seemed to be two camps, those that used editors like nano and avoided vim like Covid-19 and those that gave you the feeling that any GUI was heresy. You explained it easily, almost casually and didn't make it appear daunting at all
holy moly, as a person that’s used non-terminal apps ‘n fat IDEs, this was refreshing! thanks for this.
i personally always thought it was some ancient thing with wonky commands... it seem i was thinking of emacs...
with just learning VIM, I feel like my cat...scratching the surface to smell what's underneath. Thanks for the basics.
Thanks! This was super helpful in addition to the 'vimtutor' command. I always had fun going through that little tutorial.
We all have to start somewhere. Thanks for initiating us on this journey!
Thanks for the quick video. Just needed a refresher, not a full walkthrough. :)
Man, you save me from a big problem of getting out of VIM. I am serious!!!!
very simple and on to the point. Thank you!
Some tips I learned from working on remote servers with really unreliable connections, dialing into Unix, Solaris and the not-so-usual server kind:
- you'll find vi in pretty much ANY *nix system, doesn't matter how old, small it can be, vi, will most likely be there, so LEARN IT, some day in the fallout future you might have to work on a terminal from 1982
- You can press ESC as many times as you want, very good if you have significant input lag and you're not sure where you're standing.
- "hjkl" replaces arrow keys. Useful when you're not sure if all the keyboard signals are being sent/received with different communication protocols.
- 0 takes you to the first character of the line, $ to the last
- w takes you one word forward, b one back
- There's shells like "ksh" that leverage vi in the command line
We could go all day ! :)
Very concise and clear. Great job.
Up voted for the nice description. Saved most of my time. I just needed to learn the replace thing.
Amazing tutorial. Quick and straight to the point!
Switch from nano a while back, liking Vim a lot, always learning new things, nice tutorial. Thanks.
Thanks for saving my time
For me, it was a good intro to Vim. Thank you.
That's too funny! ...stick a noob in front of a keyboard and get him to quit vi... Hey, that was me! Based on that alone (I'm still going through your video, only at 1:52 on the timer as of this comment) I'm commenting and subscribing.
I found vim difficult so use nano. But your easy explanation will make me to try vim again. It is much easier than I thought. Thanks for the clear explanation.
6:26 Isn't it 'g' for 'global' not 'greedy'? What does it do? It replaces all occurrences on a LINE instead of just the first occurrence on a line.
basic but very good for beginner, thanks a log
Finally, someone just made a good vim tutorial
You're way better than my Linux prof
Not gona lie, I came here for :q
This video is kind off 2 years old now, but your still the Man?
I cant believe this video is upto 8mins, it seemed more like 2mins as it was really interesting to watch, I naturally like the simplicity of nano but because of you, I am gonna quit using nano and switch to vim. you should definitely make a part two.
Also, that joke about sticking a noob into a terminal running vim and them not being able to quit is soo true, faced it many times 🤣😂
what an amazing video, i like the way you memorise the codes
Best goddam intro to Vim I've come across. _Sombrero_ 🤠
Thanks for this video. Gave just enough info to get me started on vim. Appreciate it.
How can you scroll the screen and not the file so you can see your terminal commands/history?
I've yet to figure out how
Thank you, very helpful!
it's the first time I'm using VIM, and at the beginning, I was like "What annoying editor".
Can learning VIM well allow me to replace all other editors - even markdown editors and maybe even LibreOffice? Can it use images? I use markdown a lot (efficient as heck). I am learning nano now as I hope to have a server and may need to access it remotely on rare occasion. I am also trying out gedit (so easy!) and micro, but am not convinced that micro can be accessed remotely (for a noob, at least) and I know gedit cannot (I use Debian, not Ubuntu).
I like your manner of speaking here.
I love your videos. This video is great. I will be using vim. We can also use vim behaviour in any IDE so we can always be in practice.
Great video, new to linux and this helped me a lot, Thank you!
Really useful quick intro, thanks
this sounds like editing text on a new level
Because it is!
Well damn, now I can edit files from the command line, that's something I couldn't do 10 minutes ago.
Colon then (q) to quit. This is exactly what I came here to learn. Leaving now!
P.s.: In remote server when you do not have Sublume and Atom, Vim is not the only choice, there is always Pico and Nano.
And emacs too
at 7:45 how to replace a linux path as it already have slashes right ?
Thank you for the video, but how to access help and create new files?
This was actually a very helpful explanation, just what I was looking for! Great job.
I have used LInux (dabbled with Ubuntu, Debian, Debian derived distributions, Fedora, ...) and some Bash shell command line commands - the famous powerful Linux emulator tool: THE THERMINAL! /dreaded by people who are only used with GUI's , beloved by powerusers -- since about 6 years ago, but I have also spend a lot of time on OS X as I dualbooted it with Linux, in which longer time period I dabbled a lot less with Linux and the command line.
I'm not a programmer, developer, system administrator whatsoever, I don't know any programming language. (had a few python lessons which I was terrible at, score of 1/4 for a project - which I 'kind of' copied huge parts from a friend -: programming an hourglass with a visual presentation and so dreaded it pretty terribly)
But I find open-source software, the Linux and GNU philosophies, the forms of freedom you can find in it, to be pretty enchanting; so finally getting a first grasp on one of the, if not most, widely used CLI text editors across the Unix and Unix-like landscapes is pretty cool.
A computer that just works for desktop applications is very understandable, not everybody wants to thinker, break, fix, find, source, compile, fail & try again; with their computer. But it has a uniqueness to it. I've always prefered Unix & the like systems some way above Windows, even though the Linux & Unix desktops are 'scattered', if you know what I'm trying to say. Yes, I'm talking about desktop experiences/little experiments, not server and other applications.
why not just use nano for basic edits of config files? just need to remember ctrl+x
i am using a remote server on putty on mac and I am trying to copy a c code in the vim but i am not able to, I have tried everything.
the code is in my mac and I want to copy the code into the file which I have created in the remote server using vim. how do I do that.
Awesome tutorial for beginners, please do a follow up
FANTASTIC intro thank you!
Awesome but what if I accidentally hit wq a whole bunch of times and forgot to add the : first? It didnt change anything except move the cursor a couple of times and would say recording. Classic rookie mistake but I dont think I messed up my config. Thoughts?
Moving the cursor forward by word, and then starting to record a macro, probably :-D. You're fine, nothing in your config would have been affected!
Thanks a ton - for a noob like me this was soooo helpful! More basic stuff like this please!
I can't wait to learn all the things I can do with quitting
Thanks A LOT!!! Up until now I've hated this editor, simply because it was not intuitive enough...rather I didn't know hOw to freakin use it👓
One thing thats rarely mentioned on Vim videos is the need to be a touch-typer. i.e you should be able to type text with all fingers without looking at the keyboard. If you're a two finger typer, you will be missing out on 80% of what Vim is about. Seriously, Touch-Typing is a pre-requisite for successfully and fully using Vim. ...that and remapping your Caps Lock key to function as Esc.
What theme and font you are using? could you pls tell? if i am not wrong u are using zsh as well what zsh theme is this