Vim - Revision history

Conrad54418: /* Learning Vim */

2021-05-28T17:55:13Z

‎Learning Vim

Conrad54418: /* Learning Vim */

2021-05-28T17:55:03Z

‎Learning Vim

Conrad54418: /* Learning Vim */

2021-05-28T17:54:33Z

‎Learning Vim

Jrwrigh: /* ..but I want more */: point git repository link to .config/nvim directory

2021-02-04T23:23:41Z

‎..but I want more: : point git repository link to .config/nvim directory

Jrwrigh at 20:12, 9 September 2020

2020-09-09T20:12:10Z

Jrwrigh at 15:05, 4 September 2020

2020-09-04T15:05:50Z

Jrwrigh: Created page with "'''vim''' (short for "'''vi im'''proved") is a command line text editor that is ubiquitous on Linux and Unix-esque operating systems. Effectively, if it runs Linux and ''doesn..."

2020-09-04T15:04:20Z

Created page with "'''vim''' (short for "'''vi im'''proved") is a command line text editor that is ubiquitous on Linux and Unix-esque operating systems. Effectively, if it runs Linux and ''doesn..."

New page

'''vim''' (short for "'''vi im'''proved") is a command line text editor that is ubiquitous on Linux and Unix-esque operating systems. Effectively, if it runs Linux and ''doesn't'' have vim, you probably won't have any other familiar tools either.

Due to it's ubiquity, <code>vim</code> is quite often the editor of choice when working on remote systems through a terminal.

== Learning Vim ==

<code>vim</code> is a "modal" editor, which makes it different than any editor you've probably ever used; it's not a "pick-up and go" application. Learning to effectively use <code>vim</code> takes time. '''However''', by taking the time, <code>vim</code> can be ''very'' powerful and useful. Who knows, maybe you might start to want to use it as your default editor (like me!(James)).

To start, I'd suggest watching this video called [https://youtu.be/_NUO4JEtkDw Learn Vim in a Week]. It'll give you a general overview of modal editing, common conventions that <code>vim</code> uses, and how to start learning.

After that, start working through <code>vimtutor</code>. It is a tutorial for the basics of <code>vim</code> ''inside'' <code>vim</code>. This makes it an interactive tutorial, which is quite good for learning. To access it, simply run <code>vimtutor</code> from a Linux command line, and follow the instructions on screen. It's recommended to do this once a day for a week or so to get everything hammered down.

While going <code>vimtutor</code> a few times, maybe check out another video called [https://youtu.be/wlR5gYd6um0 Mastering the Vim Language]. It'll further get you familiar with how <code>vim</code> operates.

== vimrc ==

Out of the box, <code>vim</code> is ''very'' minimal. To set some sensible defaults, I'd recommend copying the [https://github.com/tpope/vim-sensible/blob/master/plugin/sensible.vim vimrc] in [https://github.com/tpope/vim-sensible sensible.vim] to your home directory. It'll get you to a more functional <code>vim</code> that's easier to work in.

== ..but I want more ==

So you want some more vim-goodness? Check out the [https://vimawesome.com/ myriad of plugins] available for <code>vim</code>. Maybe use a [https://github.com/junegunn/vim-plug plugin manager] and even start managing your settings in a [https://github.com/jrwrigh/dotfiles2.0 git repository] to keep changes persistent in different computers.

@@ Line 5: / Line 5: @@
 == Learning Vim ==
-<code>vim</code> is a "modal" editor, which makes it different than any editor you've probably ever used; it's not a "pick-up and go" application. Learning to effectively use <code>vim</code> takes time. '''However''', by taking the time, <code>vim</code> can be ''very'' powerful and useful. Who knows, maybe you might even want to use it as your default editor like me! (James)
+<code>vim</code> is a "modal" editor, which makes it different than any editor you've probably ever used; it's not a "pick-up and go" application. Learning to effectively use <code>vim</code> takes time. '''However''', by taking the time, <code>vim</code> can be ''very'' powerful and useful. Who knows, you might even want to use it as your default editor like me! (James)
 To start, I'd suggest watching this video called [https://youtu.be/_NUO4JEtkDw Learn Vim in a Week]. It'll give you a general overview of modal editing, common conventions that <code>vim</code> uses, and how to start learning.

@@ Line 5: / Line 5: @@
 == Learning Vim ==
-<code>vim</code> is a "modal" editor, which makes it different than any editor you've probably ever used; it's not a "pick-up and go" application. Learning to effectively use <code>vim</code> takes time. '''However''', by taking the time, <code>vim</code> can be ''very'' powerful and useful. Who knows, maybe you might start to want to use it as your default editor, like me! (James)
+<code>vim</code> is a "modal" editor, which makes it different than any editor you've probably ever used; it's not a "pick-up and go" application. Learning to effectively use <code>vim</code> takes time. '''However''', by taking the time, <code>vim</code> can be ''very'' powerful and useful. Who knows, maybe you might even want to use it as your default editor like me! (James)
 To start, I'd suggest watching this video called [https://youtu.be/_NUO4JEtkDw Learn Vim in a Week]. It'll give you a general overview of modal editing, common conventions that <code>vim</code> uses, and how to start learning.

← Older revision		Revision as of 23:23, 4 February 2021
Line 19:		Line 19:
	== ..but I want more ==		== ..but I want more ==

−	So you want some more vim-goodness? Check out the [https://vimawesome.com/ myriad of plugins] available for <code>vim</code>. Maybe use a [https://github.com/junegunn/vim-plug plugin manager] and even start managing your settings in a [https://github.com/jrwrigh/dotfiles2.0 git repository] to keep changes persistent across different computers.	+	So you want some more vim-goodness? Check out the [https://vimawesome.com/ myriad of plugins] available for <code>vim</code>. Maybe use a [https://github.com/junegunn/vim-plug plugin manager] and even start managing your settings in a [https://github.com/jrwrigh/dotfiles2.0/tree/master/.config/nvim git repository] to keep changes persistent across different computers.

← Older revision		Revision as of 15:05, 4 September 2020
Line 2:		Line 2:

	Due to it's ubiquity, <code>vim</code> is quite often the editor of choice when working on remote systems through a terminal.		Due to it's ubiquity, <code>vim</code> is quite often the editor of choice when working on remote systems through a terminal.
−

	== Learning Vim ==		== Learning Vim ==

@@ Line 11: / Line 11: @@
 After that, start working through <code>vimtutor</code>. It is a tutorial for the basics of <code>vim</code> ''inside'' <code>vim</code>. This makes it an interactive tutorial, which is quite good for learning. To access it, simply run <code>vimtutor</code> from a Linux command line, and follow the instructions on screen. It's recommended to do this once a day for a week or so to get everything hammered down.
-While going <code>vimtutor</code> a few times, maybe check out another video called [https://youtu.be/wlR5gYd6um0 Mastering the Vim Language]. It'll further get you familiar with how <code>vim</code> operates.
+While going <code>vimtutor</code> a few times, maybe check out another video called [https://youtu.be/wlR5gYd6um0 Mastering the Vim Language]. It'll further get you familiar with how <code>vim</code> operates and it's general conventions. This video in particular is what turned me (James) into a vim zealot of sorts.
 == vimrc ==
@@ Line 19: / Line 19: @@
 == ..but I want more ==
-So you want some more vim-goodness? Check out the [https://vimawesome.com/ myriad of plugins] available for <code>vim</code>. Maybe use a [https://github.com/junegunn/vim-plug plugin manager] and even start managing your settings in a [https://github.com/jrwrigh/dotfiles2.0 git repository] to keep changes persistent in different computers.
+So you want some more vim-goodness? Check out the [https://vimawesome.com/ myriad of plugins] available for <code>vim</code>. Maybe use a [https://github.com/junegunn/vim-plug plugin manager] and even start managing your settings in a [https://github.com/jrwrigh/dotfiles2.0 git repository] to keep changes persistent across different computers.