ctrlp.vim VS vim-fugitive

ctrl-p

use a fuzzy finder, I like https://github.com/nvim-telescope/telescope.nvim (when I was a vim user, it was https://github.com/kien/ctrlp.vim)

Ctrlp.vim existed prior to VSCode.

Fuzzy file search: fzf, ctrlp

" --- VUNDLE --- set nocompatible " be iMproved, required filetype off " required " set the runtime path to include Vundle and initialize set rtp+=~/.vim/bundle/Vundle.vim call vundle#begin() " alternatively, pass a path where Vundle should install plugins "call vundle#begin('~/some/path/here') " let Vundle manage Vundle, required Plugin 'VundleVim/Vundle.vim' " The following are examples of different formats supported. " Keep Plugin commands between vundle#begin/end. " plugin on GitHub repo Plugin 'tpope/vim-fugitive' " plugin from http://vim-scripts.org/vim/scripts.html " Plugin 'L9' " Git plugin not hosted on GitHub Plugin 'git://git.wincent.com/command-t.git' " git repos on your local machine (i.e. when working on your own plugin) "Plugin 'file:///home/gmarik/path/to/plugin' " The sparkup vim script is in a subdirectory of this repo called vim. " Pass the path to set the runtimepath properly. Plugin 'rstacruz/sparkup', {'rtp': 'vim/'} " Install L9 and avoid a Naming conflict if you've already installed a " different version somewhere else. " Plugin 'ascenator/L9', {'name': 'newL9'} " All of your Plugins must be added before the following line Plugin 'Valloric/YouCompleteMe' Plugin 'preservim/nerdtree' call vundle#end() " required filetype plugin indent on " required " To ignore plugin indent changes, instead use: "filetype plugin on " " Brief help " :PluginList - lists configured plugins " :PluginInstall - installs plugins; append `!` to update or just :PluginUpdate " :PluginSearch foo - searches for foo; append `!` to refresh local cache " :PluginClean - confirms removal of unused plugins; append `!` to auto-approve removal " " see :h vundle for more details or wiki for FAQ " Put your non-Plugin stuff after this line " --- NATIVE --- syntax on set tabstop=4 softtabstop=4 set shiftwidth=4 set expandtab set smartindent set nu set relativenumber set nowrap set smartcase set noswapfile set nobackup set undodir=~/.vim/undodir set undofile set incsearch " --- VIM-PLUG --- call plug#begin() Plug 'morhetz/gruvbox' Plug 'jremmen/vim-ripgrep' Plug 'vim-utils/vim-man' Plug 'mbbill/undotree' Plug 'https://github.com/kien/ctrlp.vim.git' call plug#end() colorscheme gruvbox set background=dark if executable('rg') let g:rg_derive_root=true endif let mapleader = " " let g:netrw_browse_split=2 let g:netrw_banner=0 let g:netrw_winsize=25 let g:ctrlp_use_caching=0 " --- REMAPPING --- " shift movement one key to the right noremap j h noremap k j noremap l k noremap ; l noremap h : " jj to escape from insert mode imap jj " --- COMMANDS --- " f9 runs current python script " normal mode autocmd FileType python map :w:exec '!python3' shellescape(@%, 1) " insert mode autocmd FileType python imap :w:exec '!python3' shellescape(@%, 1)

Set vim as your default text editor, that could give you additional motivation :) regarding plugins, it really depends of what you use now, but there are still some great general-use plugins: ctrl + p nerdtree git blame ack to beggin with

check nerdtree and ctrlp

Ctrl+p: A plugin to quickly jump to a file by name.

To open your files, use something like ctrl-p Alternative is fzf.vim

the only reason I do some git stuff in vim and not _always_ in the shell, is because tpope is very thoughtful and fugitive.vim provides nice ways to deal with hunks or hunk partials (visually selecting a range within a hunk, for i.e.)

https://github.com/tpope/vim-fugitive/blob/master/doc/fugiti...

I agree, navigating blame history is incredibly useful, if only to save you from asking the wrong person about a particular change.

Vim's Fugitive[1] can do this and also in Textmate to. So I would hope that most editor git plugins can.

1. https://github.com/tpope/vim-fugitive

Git: vim-fugitive and gitsigns.nvim

You'll want to invest the time in learning Magit, which will change your life once you get the hang of it (and I was a heavy user of Fugitive in Vim previously!), and it's unlikely you'll find a better integration with GDB anywhere else on the planet than with Emacs, though I can't say that empirically. You just need to take the plunge and start learning it, then cut over and take the hit in productivity one day when you're feeling adventurous. You'll ultimately become far more powerful than you've ever been. Especially if you delve into elisp over time. I use Spacemacs, which is bloated and has bugs, but it has so many features that I haven't undertaken the massive endeavor to replace it from scratch yet.

For an option that works on Vim, if you already use tpope's vim-fugitive, there's vim-rhubarb (for GitHub) and fugitive-gitlab.vim (for GitLab).

I replace vim-fugitive with :! git

The only thing I truly miss from Emacs is [Magit](https://magit.vc/) since I still consider it the best git wrapper available. It is just too good. Unfortunately [Neogit](https://github.com/TimUntersberger/neogit) is not quite there yet although I hope it makes it at some point. I didn't like [Fugitive]https://github.com/tpope/vim-fugitive), but I ended up finding a good enough workaround by using [Lazygit](https://github.com/jesseduffield/lazygit) through [Toggleterm](https://github.com/akinsho/toggleterm.nvim).

I do think VSCode is a great tool and I recommend it frequently to people, but I still want to set the record straight here. Yes, vim is obviously limited in the sense that as a CLI app it doesn't draw it's own PDF or HTML windows, that's fair. But it can remote control your favorite PDF viewer or browser for roughly the same functionality. I'm currently writing my thesis using vimtex and it's quite smooth. And all the other stuff you mention is implemented quite competently by various plugins like vim-fugitive, coc.nvim, vimspector and copilot.vim.

Edit: je viens de trouver [https://github.com/tpope/vim-fugitive de Val