junegunn / junegunn/fzf.vim

Could use a section on post-install updates.

Open
#823 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Vim Script
Stars
10.3k
Forks
608
Avg merge
5d 8h
Merged PRs (30d)
2

Description

- Category
- [ ] Question
- [ ] Bug
- [x] Suggestion
- OS
- [ ] Linux
- [ ] macOS
- [ ] Windows
- [ ] Etc.
- Vim
- [x] Vim
- [ ] Neovim

Install script writes things to rc files, which is helpful, but with nothing but the ./install script documenting the changes made, the upgrade flow feels less than clean. For me personally, if I'm going to have to go through the install script manually to see how to perform an upgrade, the advantage of having the install script automate the initial install is significantly reduced (because it hides from me details I'm going to need to know to keep things up to date). Perhaps the documentation could list the changes made, in such a way as to give users the option of copying them into their rc files themselves, or letting the install script handle it.

Is there a recommended approach to upgrade that I've missed? I'm using both fzf and fzf.vim, though I currently use Vundle and/or Pathogen for plugin management, so the vim-plug approach to updating from Vim isn't really an option for me.

Thanks,
Brett S.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.