mhinz / mhinz/vim-galore

Packages: why a manager?

Open
#165 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Vim Script
Stars
18k
Forks
627
PR merge metrics
No merged PRs in 30d

Description

I’m a long time vim user and this is something I still struggle with: sure, I can use a package manager, but why should I, given vim8? And what criteria should I use to evaluate the various PMs?

(Great doc, btw, learned a lot… things have changed a great deal since I started with vi 32 years ago and returned to daily in depth vim after a 20+ year hiatus.)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Review the guide and the Vim 8 context raised in this issue before planning the documentation change. Explain why a package manager can still be useful with Vim 8 and provide criteria for comparing package managers; the work is done when both questions are addressed clearly in the guide.

Written by the indexing model from the issue text.

Assessment

Tech stack
vim
Domain
documentation
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.