vi is a text editor for programmers, designed to facilitate optimal efficiency
when writing code.
vi, simply type the following:
$ vi [filename]
This will open a file with the name specified. If there is an existing file with that name, it will open that file, however if no file is found with that name, a new, empty one will be created.
Since its creation, the developers have also released
vim (vi improved), an
updated version with more features, such as support for more programming
languages, compatibility with more OS’s, and features like multilevel undo/redo.
On some Linux distributions, the
vi executable provided is actually vim.
Despite this, some programmers still prefer
vi over vim for its simplicity
and ease of access.
Because vim is Difficult, But Awesome.
vim is infamous among programmers for its steep learning curve.
Because vim was designed to be used in a command-line interface, it’s entirely
controlled with keyboard shortcuts. Most of the “standard” keyboard shortcuts
that we’re familiar with (e.g.
CTRL-a for “select all”,
CTRL-c for “copy”)
either won’t work in vim, or they won’t do what you’d expect without some
That reliance on keyboard commands is a blessing and a curse. On one hand, it makes vim difficult to learn. On the other hand, because you can control vim without ever removing your hands from the keyboard, skilled vim users can edit code very, very quickly.
Using vim, you can…
…record macros to make writing test cases less repetitive…
…select text and toggle between uppercase and lowercase…
…and edit text in blocks, not just line-by-line or character-by-character.
Here are some basic commands to get you started:
esc- enter command mode
l- move cursor left, up, down, and right respectively.
i- enter insert mode
s-Delete character and enter insert mode
a- insert after character
v + [direction]- select text with cursor
:w- write/save file
:q- quit vim
d$delete to the end of the line
dddelete entire line
y- yank/copy selected text
p- put/paste yanked text
r + [character]- replace character at cursor with specified character
u- undo action
ce- replace text until end of word
/ + [search phrase]- search file for specified phrase
For a more complete tutorial, run:
in a Linux terminal, or visit this link.
Introduction to Modal Editing
vimtutor covers the basics of using vim better than we can here, but it
doesn’t spend much time explaining one of vim’s less intuitive features: modal
Unlike a word processor like Google Docs, or an IDE like Xcode, vim’s behavior (i.e. what will happen when you press a key) changes based on its current mode. The modes you’ll use most frequently in vim are normal mode, insert mode, and visual mode,
We’ll start with insert mode because it’s the easiest to understand.
Insert mode is the mode that lets you insert text into a file. Using insert mode
is similar to editing text files in nano. You can move your cursor using the
PgDn, and most of the other navigation keys
you’re used to using.
Del do what you’d expect, and you add
text just by typing.
CTRL-RightArrow (for moving the cursor one
word left or one word right, respectively) may or may not work, depending on
your terminal or your current shell environment.
CTRL-Backspace (for deleting
the entire last word) almost certainly won’t work. Thankfully, the
equivalent bash shortcuts will!
Here’s a snippet of some bash shortcuts that you may want to use:
||Deletes previous word.||
||Move one word back.||
||Move one word forward||
||Move to start of line.||
||Move to end of line.||
META key is usually the
ALT key. You may have to do some
finagling to get it working on your machine.)
(Also, most of the shortcuts above aren’t that useful in insert mode, with the sole
CTRL-w for deleting a word. We’ll explain why when we cover
There are many ways to enter insert mode:
i: Enters insert mode at the cursor’s current position.
a: Enters insert mode, moving the cursor to the position after the current character.
I*: Enters insert mode at the start of the current line.
A: Enters insert mode at the end of the current line.
s: Substitute. Delete the currently selected text and enter insert mode.
r<CHAR>: Replace the currently selected character(s) with
SHIFT-i. Typing an
CAPS LOCK turned on will also
(** Replace is a bit of a special case: it doesn’t actually enter insert mode, and it’s a special command in and of itself. It replaces every character that you have highlighted with the next character you type and immediately returns you to normal mode.)
Normal mode, as its name suggests, is the mode you’ll spend the most time using. You start in normal mode when you launch vim, and you return to normal mode when you exit another.
This is counterintuitive for many people because they’re used to text editors and word processors that almost always “stay in insert mode” (e.g. nano, gedit, Microsoft Word, LibreOffice Writer, etc.) Many novice vim users spend all of their time in insert mode, only entering normal mode to save their work and to close vim.
Editing exclusively in normal mode defeats the entire purpose of using vim! By itself, insert mode is nothing but a less capable clone of nano. Insert mode exists just because, were it omitted, vim wouldn’t be a text editor. The bulk of vim’s most useful features lie in normal mode and in visual mode.
Normal mode’s featureset can be roughly divided into the following categories: basic editor essentials, navigation, and doing weird stuff,
Basic Editor Essentials
Things like saving files, opening new files, opening new tabs, splitting the current window (i.e. opening multiple files side-by-side), and closing vim are done from within normal mode.
You can almost always return to normal mode by pressing
You’ll recall that we recommend not using the
to skip back/forward one word from within insert mode. That’s because one of the
primary purposes of normal mode is fast file navigation.
Normal mode has a number of keybindings that make navigating files easier. We provide a non-exhaustive list of them below:
Basic Navigation Keys
hjkl: Respectively, move (left/down a line/up a line/right).
CTRL-u: Go up half a page.
CTRL-b: Go up a full page.
CTRL-d: Go down half a page.
CTRL-f: Go down a full page.
gg*: Go to the start of the file.
G: Go to the end of the file.
(* no re)
Navigation Within a Line
w: Move the cursor to the start of the next word.
W: Move the cursor to the start of the next WORD.
b: Move the cursor to the start of the current word.
B: Move the cursor to the start of the current WORD.
e: Move the cursor to the end of the current word.
0: Move the cursor to the start of the current line.
^: Move the cursor to the first non-whitespace character in the current line.
$: Move the cursor to the end of the current line.
Search Within a Line
f<CHAR>: Search for the next instance of
<CHAR>in the current line.
F<CHAR>: Search backwards in the current line for the nearest instance of
fsearch): Jump to the next instance of
<CHAR>in the current line.
fsearch): Jump backwards to the nearest instance of
<CHAR>in the current line.
Fsearch): Jump backwards to the nearest instance of
<CHAR>in the current line.
Fsearch): Jump forwards to the nearest instance of
<CHAR>in the current line.
Doing Weird Stuff
u: Undo the last action.
CTRL-r: Redo the last undone action.
<<: Decrease the indentation of the current line
>>: Increase the indentation of the current line
d<MOTION>: Cut the characters the cursor would cross over if you were to perform
dd: Cut the current line.
=<MOTION>: Fix the indentation of the lines the cursor would cross over if you were to perform
zz: Center the screen on the cursor.
zt: Move the screen so that the current line is at the top.
zb: Move the screen so that the current line is at the bottom.
Modern text editors, web browsers, PDF viewers, etc. allow you to select ranges of text by clicking and dragging with the mouse. In vim, you would do the same using visual mode.
:help gives the following description of visual mode:
Visual mode is a flexible and easy way to select a piece of text for an operator. It is the only way to select a block of text.
Operators allow you to edit text in bulk. Cutting, copying (“yanking”), and pasting (“putting”) in vim requires the use of operators.
Cut, Copy, and Paste
Basic copy-pasting makes use of the unnamed register (
""). This register is
like a bucket filled with the text most recently grabbed by any of the
- Text deleted using the
- Text replaced using the
- Text “yanked” using the
To copy and paste text, highlight some text in visual mode, then yank with
Move the cursor where you want, then paste it there using
p. (You can insert
the pasted text at the position before the cursor with
To cut text, highlight text in visual mode, delete it with
s), then paste using the same process described above.
The screencasts in the subsections below demonstrate how this works.
The Different Visual Modes
-- VISUAL --
The basic visual selection mode. Analogous to highlighting text in an “ordinary” text editor by holding down the left mouse button and dragging the cursor over text.
To use, move the cursor to the start of the text, then press
v. Move the
cursor to the end of the text that you want to select. Note that you can –
and generally should – use the “special” normal mode navigation keys (
etc.) to select the text range you want. Moving the cursor backwards
k, etc.) will also work.
-- VISUAL LINE --
Used for selecting entire lines of text at a time. The mode you’ll probably use
most frequently, at least when programming. To use, move the cursor to the first
line you want to select, then press
-- VISUAL BLOCK --
Used for select rectangular blocks of text. Though it can be used for cutting and pasting, it’s often used to perform precise edits on multiple consecutive lines at a time.
Visual block mode has special behavior when used in conjunction with insert
mode. Selecting a visual block and substituting it by pressing
s allows you
to replace each line in your selected block with the text you type. Selecting a
visual block and prepending text with
I will prepend text onto each line, while
A will append text onto each line.
This mode is one of the most compelling arguments to indent with spaces, or at least to indent with tabs and use spaces for alignment.
To use, move the cursor to a corner of the text you want to select, then press
Unlike more basic text editors like gedit, vim’s interface and functionality
are both extremely configurable. vim has its own scripting language
vimscript) that lets you
customize vim in a number of ways, either by editing your
configuration file, or by writing plugins.
.vimrc is a dotfile that
lives in your home directory (e.g.
short). It’s written entirely in vimscript, and vim will
source it (i.e.
execute the contents of the file, line-by-line) whenever you launch vim.
.vimrc is a config file, first and foremost. It’s like a text-only
version of the
Edit > Preferences menu in a GUI text editor. You can use it to
change settings (e.g. whether or not to show line numbers, what colorscheme to
use) or change vim’s default keymappings to suit your needs. Changing these
settings is just a matter of editing your
.vimrc in a text editor, saving, and
then opening a new instance of vim.
A vim user’s
.vimrc is a very personal thing. It’s like working on a car that
you drive every day. Putting in that added effort is a non-negligible amount of
work, but once it’s done, the car runs exactly how you’d like.
(Unlike a car, however, once you customize vim enough, your vim installation will be completely unusable by anybody except yourself.)
The settings in Tim Pope’s sensible.vim
are a good starting point for a personal
.vimrc. You can find many online
quick-start guides offering tips for vim beginners, as well.
Version Control and the
.vimrc is literally just a text file, it makes your vim
installation very portable. Oftentimes, vim users will manage their
using a version control system such as git, storing it “in the cloud” on sites
like GitHub or BitBucket. If a vim-using Michigan student doesn’t have access
to their laptop and wants to edit a text file on a CAEN computer, installing
their personal vim configuration is just a matter of:
git clone https://firstname.lastname@example.org/billy_magic/vimrc.git ~/vim_config ln -s ~/vim_config/.vimrc ~/.vimrc
What this command does is:
git clone https://email@example.com/billy_magic/vimrc.git ~/vim_config ^ clone a local copy of a git repository... ^ ...from billy_magic's personal BitBucket account... ^ ...and store it in a folder named vim_config in his home directory. ln -s ~/vim_config/.vimrc ~/.vimrc ^ Then making a symlink... ^ ...pointing to the .vimrc in that folder... ^ ...and putting that symlink in the default location for a .vimrc. Now, when vim tries to read ~/.vimrc, Linux will redirect it to ~/vim_config/.vimrc
This student will have immediate access to the exact same keymappings and
settings that they normally use in vim. Because their
exists in their home directory on CAEN, those settings will be loaded
automatically whenever they log into a CAEN computer.
The beautiful thing about doing this is that, if Billy Magic modifies his
.vimrc on his personal computer and
git pushes his changes, all he has to do
to copy those same changes to CAEN is
cd ~/vim_config && git pull.
This is especially handy if you’re prone to accidentally nuking the bajeezus out of your Linux installations. You still have to reinstall everything from scratch, but reinstalling vim and restoring your settings will take minutes at most.
Placing your entire vim configuration in the file named
.vimrc is a lot like
writing an entire EECS project in
main(): it’s perfectly doable with simple
projects for classes like ENGR 101 and EECS 183, but things will get ugly fast
if you attempt the same in EECS 281. Similarly, maintaining a
.vimrc is easy
when you’ve just started using vim, but it’ll grow more difficult as that
.vimrc grows in size.
Remember that vimscript is a Turing complete programming language in and of
itself. You will, at times, need to debug your
.vimrc. This is much easier if
you separate your
.vimrc into smaller
.vim files that you
source in your
Many of the niceties that you’re used to having in a more modern text editor aren’t baked into vim by default. In theory, you could implement these yourself in vimscript, but writing a time- and memory-efficient implementation of tab autocompletion in vimscript is far more effort than it’s worth.
Thankfully, you don’t need to. vim has a vibrant community of plugin authors that have already done much of the heavy lifting. Of these, Tim Pope and Martin Grenfell (a.k.a. scrooloose) are some of the most prolific.
Because vimscript is an interpreted language, having access to a vimscript
executable is the same as having the original vimscript source code. This allows
developers of vim plugins to distribute their plugins through GitHub. Installing
these plugins is a matter of
git cloneing the plugins into the appropriate
directories on your machine.
Although vim does have built-in support for plugins, that support is fairly rudimentary. You’ll want to use a plugin manager to install and update plugins, especially as the complexity of your vim installation grows.
Two of the most popular plugin managers are:
Tim Pope’s pathogen.vim is notable in that it effectively created the standard layout of a vim plugin. It is actually considered bad programming practice among vim developers to write a plugin that doesn’t use a pathogen-compatible directory structure.
pathogen.vim takes its name from the fact that it modifies vim’s
runtimepath. Without going into too much detail, that means that vim will
source the vimscript files of plugins provided that the plugin:
- Adheres to the pathogen-standardized directory structure
- Was cloned into
In simpler terms, once you’ve installed pathogen.vim (both the plugin itself,
and the lines you need to add to your
.vimrc), you can install plugins by
cd ~/.vim/bundle git clone https://github.com/plugin_author/the_plugin_you_want_to_install.git
More detailed instructions can be found on pathogen’s GitHub page.
You can think of Vundle as being a convenient wrapper around the functionality of pathogen.vim. They both do essentially the same thing, but pathogen.vim is a bit leaner while Vundle has a few features that simplify managing lots of plugins at the same time.
git cloneing the GitHub repositories of the plugins you want directly
~/.vim/bundle folder can be tedious; automating the process of doing
that, generating helptags (so that
:help <PLUGIN_NAME> will actually do
git pulling when you want to update your plugins is doable,
but it’s non-trivial work that requires a bit of shell scripting.
To use Vundle, you add some lines to your
.vimrc, list the plugins you want to
install between them, and run the vim command
:PluginInstall. To update your
plugins, you run
:PluginUpdate. To remove the cloned repositories of plugins
that you no longer list in your
.vimrc, you run
More detailed instructions can be found on Vundle’s GitHub page.
An Aside: vim vs. neovim
vim is an old piece of software, and it’s largely maintained by one person, Bram Moolenaar. It contains a great deal of legacy code for decades-old computer systems, and the fact that it only has one maintainer slows the speed of its development.
In 2014, a few programmers decided to make their own fork of vim to try and fix these issues. Enter neovim. neovim is to vim as Linux Mint is to Ubuntu: it’s a different flavor of the same basic thing. On top of vim’s featureset, neovim offers:
- A “remote plugins” API that allows developers to write plugins in languages other than vimscript (usually, Python). These tend to be faster and more capable than plugins written in vimscript.
- Nicer default settings to reduce the time you need to spend fiddling with the
.vimrcright after installation. For instance, neovim enables mouse support by default.
- Native support for multithreading (“asynchronous jobs”). Newer versions of vim do support this, but they didn’t when neovim was first released. In the past, vim and its plugins would run entirely on a single thread; this meant that resource-hungry plugins (like autocompletion plugins, syntax checkers, ctags generators, and so on) would block the code handling vim’s user interface, effectively freezing it until that plugin finished what it was doing.
- A terminal emulator. Yes, you can run an instance of neovim inside neovim.
neovim’s killer app is probably lldb.nvim, an integrated graphical debugger similar to what you can use in an IDE. Similar plugins are available for vim, however, notably vim-lldb, from which lldb.nvim was forked.
vim has the advantage of being preinstalled on most modern Linux machines, including CAEN. Sticking with standard vim means that you can carry your vim installation with you to practically any Linux machine you ever need to use. neovim, on the other hand, is (arguably) easier to set up for a first-timer, and supports a broader range of plugins, many of which aren’t compatible with vim proper. Even so, it’s still largely cross-compatible with vim: switching to vim on a machine that doesn’t have neovim is usually just a matter of losing one or two plugins that you might have liked using.
Whether to use vim or neovim is mostly a matter of personal choice. Use whichever is most comfortable for you!
Using vim vs. Using an IDE
A “vanilla” installation of vim is like a supercharged version of a standard text editor, but it doesn’t have many of the niceties that would make it useful for a programmer. It doesn’t include, for instance:
- An automatic drop-down menu for text autocompletion
- Code linting/syntax checking
- A graphical debugger
- A (good) file browser
And so on. For these reasons, many programmers will recommend using vim for small, repetitive tasks – things that can be done quickly and easily with vim’s robust text editing tools – while performing the actual “meat” of development and debugging in an IDE like Visual Studio or Xcode.
If all you need is a working IDE, you’re probably better off using a
purpose-built IDE. You won’t necessarily have access to the most awesome parts
of vim (e.g. macros, “visual block” text selection, etc.), but the time that
costs you is easily outweighed by the time you’d save using an IDE’s graphical
debugger and syntax checkers. With stock vim, your only real way to check for
syntax errors is to
make your code and read through the errors, and your only
debugging tools are those that you can run from the command line in another
terminal. Command line debuggers like GDB and LLDB are very capable, but for
small tasks like setting breakpoints and inspecting variable values, you’re
better off with an IDE.
But, if you’re willing to put in the time, you can make vim work like an IDE. You can accomplish this with the use of plugins.
Installing and configuring these plugins is a bit of a pain, unfortunately. You can find a good list of plugins that provide IDE-like functionality here.
Things to Learn
Some neat features that vim offers without needing to install plugins. (There’s some overlap between the information given here and some of the sections above, but these should go into more detail.)
- Mapping Keys in Vim
- Changing keymappings is one of the simplest and most important parts of configuring your vim installation.
- Might we recommend
inoremap jk <ESC>and
vnoremap jk <ESC>? That lets you exit insert mode and visual mode by hitting
kin quick succession. It’s faster than hitting
<ESC>, you don’t have to move your left hand, and it lets you finish a text insertion or text selection with your fingers already on the home row.
- HJKL, WB, E: Real Vim Users Don’t Use Arrow Keys
hjkl, the basic navigation keys, are accessible without moving your hands from the home row.
emake it much less annoying to navigate within a line.
count: Repeat the Next Command
- Relatively self-explanatory. If
jin normal mode moves you down by one line,
10jmoves you down ten lines. Pressing
iin normal mode, then typing
<ESC>inserts the text
harbaughinto your file. Pressing
10iin normal mode and doing the same inserts ten
harbaughs into your file. And so on.
- If only there was a way to see how far away a given line was from your current position? That would make jumping between blocks of code much faster…
- Relatively self-explanatory. If
- Rapid File Navigation with Relative Line Numbering
- Jump around your text files like a jackrabbit that’s been fed coffee grounds. Nothing but coffee grounds, till the end of its days.
- Text Searching
- Find something in the current file.
- Search Patterns (a.k.a. Regular Expressions)
- What if you don’t want to search for the specific string
"12345 Arbor St.", but instead want to search for all address-like strings in the current file?
- What if you don’t want to search for the specific string
- Search and Replace
- Like find and replace, but much more powerful.
- Supports standard search and replace (i.e. find this exact string, replace it with this exact string), but also regular expressions (“regex”), ranges (i.e. replace between this line and this line) as well as command-line-esque “flags” for special behavior.
- Mr. Worldwide: The
- Let’s say you have a Linux log file that’s tens of thousands of lines long,
and you want to delete every line that doesn’t contain the string
"NetworkManager". You can do this with a single vim command.
- Let’s say you have a Linux log file that’s tens of thousands of lines long, and you want to delete every line that doesn’t contain the string
- Recording Macros and Macro Playback
- Record a series of keystrokes that you can play back by hitting
@followed by a letter. For when you need to repeat a short, repetitive, complicated task that would be hard to automate programmatically.
- These macros pair nicely with the special navigation keys given above (
b, etc.), since they’re more “intelligent”. Recording basic navigational movements (
hjkl) is akin to hardcoding a program to only read in a specific number of lines.
- Record a series of keystrokes that you can play back by hitting
- Visual Selection
- Highlight text without using the mouse. Highlight character-by-character or line-by-line. Highlight rectangular boxes of text.
- Pairs very nicely with vim’s special navigation keys, especially when you
couple them with
- Toggle Case
- That thing you’ve probably wanted to be able to do in text editors for a while.
- Copy-Pasting: Yanking and Registers
- Copy-pasting to/from the system clipboard, if that functionality is enabled on your machine.
- Having multiple places into which you can copy-paste. Handy, in some situations.
- Paste Mode: When the
+Register Doesn’t Work
- There are some places where you don’t have access to the system clipboard (e.g. Windows Subsystem for Linux, while SSHing into CAEN). This gives you the ability to paste in those situations, though you can’t copy.
- Split Buffers
- View multiple files side-by-side, or open multiple views of the same file at different positions.
- If you use neovim, you can open a terminal side-by-side with a text file and copy-paste from one into the other.
- Collapse a selected text range, hiding it from view. Open it again if you’re interested in what’s there, hide it again if it’s getting in the way.
- Open two files side-by-side in a vertical split. Automatically fold sections of the files that are identical. Highlight the lines that are different.
vimdiffis actually just an alias for
vim -d. If you use neovim, you can launch a
vimdiffinside neovim using
- Tabs in Vim
- For when you start working on those large coding projects.
Some of these require a great deal of hair-pulling and frustration to properly set up. These plugins are loosely sorted by usefulness and ease of installation, with more useful/easier to install plugins near the top.
vim-surround (GitHub Link)
Convenient keymappings for working with text that lies “between” things, whether they be curly braces, parenthesis, quotation marks, HTML tags, and more.
vim-unimpaired (GitHub Link)
Convenient keymappings wrapping around some of vim’s less intuitive commands.
nerdtree (GitHub Link)
A file explorer for vim that opens in a “sidebar” (actually a narrow vertical split.)
localvimrc (GitHub Link)
.lvimrc files in when in certain directories. Useful when hopping
between two codebases adhering to different style guides (e.g. one indents with
tabs, the other spaces). Pairs nicely with neomake and syntastic, since it lets
you set your syntax checker’s compiler settings per-project by putting
files in those projects’ directories.
fugitive (GitHub Link)
git integration within vim. On top of letting you
git pull, etc., also allows you to browse the entire git history of a
syntastic (GitHub Link)
The most popular syntax checker for vim. Runs your code through an external
syntax checker (usually
g++, for us EECS students) and tells you when you’re
doing something wrong.
Needs some extra configuration when working within large codebases. If your
#includes system headers (for libraries like
boost) or even just
.hpp files from another directory, you’ll have to provide syntastic with
-I flags. See the GitHub README’s section on
passing arguments to a syntax checker.
Note that this is done in a
.vimrc file. With localvimrc, it can be done in a
.lvimrc file as well.
neomake (GitHub Link)
Another syntax checker for vim whose main selling point is asynchronous execution (i.e. syntax checking won’t momentarily freeze vim, since it happens “in the background”). Originally written for neovim, but now compatible with vim as well. It doesn’t seem that syntastic will get async support anytime soon, unfortunately.
Note that neomake is like syntastic in that its “makers” won’t
directories unless provided with the appropriate command line flags. Again, you
can configure this in your
.vimrc, or in
.lvimrc files if you have
vim-easytags (GitHub Link)
Automatically generate ctags from
inside vim. Move your cursor over a custom type and hit
CTRL-] to jump to the
definition of that type. Pairs well with tagbar.
Make sure to turn on its async support. vim-easytags stores its ctags in a sorted list; as time goes on, that list becomes large, and having your vim freeze every ten minutes or so to update that list will get annoying after a while.
Also, don’t recursively generate ctags from within
/usr/include because you
want to be able to
CTRL-] custom types from open-source libraries. You’ll get a
tags file that’s literally gigabytes in size.
tagbar (GitHub Link)
Lets you open a sidebar listing function definitions in the current file. Useful
when working with very large
.cpp files. Because it relies on ctags, pairs
well with vim-easytags, which makes ctag generation a background process.
vim-snippets (GitHub Link)
Create “templates” that you can drop into text files. Useful for writing documents in LaTeX, inserting comment blocks of predetermined length, and so on. The backend for plugins like UltiSnips.
UltiSnips (GitHub Link)
Provides a convenient interface for creating, editing, and inserting snippets.
vimtex (GitHub Link)
A bunch of things that are handy for editing TeX files. Among other things, lets you do the thing where you view a “live” compiled PDF of your current TeX file next to your editor in SumatraPDF or similar.
Uncooperative (But Very Useful) Plugins
Some assembly required.
lldb.nvim (GitHub Link)
Mentioned above. neovim only. Gives you an IDE-like debugging interface from
inside neovim where you can step through code, set breakpoints on lines, etc.
clang and some additional Python code as a backend.
clang on Ubuntu so that lldb.nvim can use it is a bit
squirrely. See this question on
StackOverflow for more information.
YouCompleteMe (GitHub Link)
Autocompletion for vim. A bit bulky; written before vim had native async support and without the benefit of neovim’s remote plugins, so installing it requires compiling an executable. More “tried and true” than the others, however.
deoplete (GitHub Link)
Autocompletion for neovim that uses neovim’s async API. Less bulky than
YouCompleteMe, but getting its
C++ semantic completion to work is
nvim-completion-manager (GitHub Link)
Autocompletion for neovim using neovim’s async API. Allegedly better-written than deoplete.