vim-highlightedyank VS vim-pathogen

Yesterday I discovered the YankTextPost autocommands-event and I get fairly excited. After having wondered how can I use it, I decided to write my own plugin for highlighting yanked text because it is a feature that I love. In-fact I have been using https://github.com/machakann/vim-highlightedyank for long time and I know that are other plugins around that serve for the same purpose.

Are you try https://github.com/machakann/vim-highlightedyank?

I was not aware of this and used vim-highlightedyank instead. I tried vim.highlight.on_yank just now. It seems that the highlight persists after pasting and the timeout works incorrectly when making successive yanks within the timeout period. So vim-highlightedyank could be a better choice if you prefer a longer timeout.

Someone also mentioned vim-highlightedyank. After a yank, that yanked region is highlighted for a brief second. Also provides good visual feedback

vim-highlightedyank to highlight the yaked text for a sec

The person who mentored me the most when I was getting started with Terraform used VIM with pathogen but honestly this isn't a great idea unless you're really invested in a VIM workflow.

I'm no networking expert, but I think something is wrong with the URL being accessed to download the file. To simplify, just go inside the ~/.vim/autoload folder, create a file named pathogen.vim, open the file, paste the contents of this file and save.

I am a bit confused. What has this anything to do with your original question? vim-pathogen is for Vim editor itself, not for PyCharm. I don't know much about MacOS, so not sure how to help. Did you try the installation steps at https://github.com/tpope/vim-pathogen ?

Back in the old(ish) days of Vim, usage of tpope/vim-pathogen to manipulate runtimepath was a popular way to install plugins. As it got update 9 days ago, it might be still used by some.

To install any plugin using Pathogen plugin manager, you need to configure PAthogen in your vimrc if you have not done it already. You can find the installation docs on Pathogen.vim. After Pathogen has been configured in your vimrc, you can clone the git repository of that plugin into your local machine and then activate it using Pathogen.

Pathogen

git clone https://github.com/tpope/vim-pathogen ~/.vim/bundle

With vim 7.4, there was some tuning to do to manage the runtime path, that's why there are a bunch of plugin managers out there, like the minimalistic, solid vim-pathogen by Tim Pope (again!), vundle, then asynchronous and fast dein, and my favorite Vim-Plug.

I think that's it... it's a very easy and light-weight setup using pathogen in my opinion. Vim now has its own package management built-in, but I still find pathogen easier. Also, you can skip the $HOME env var if you want... I just like giving Vim and other $HOME respecting programs their own place because c:\Users\ is usually filled with other junk.