Galooshi / Galooshi/vim-import-js
Use <Plug> mappings
Open
enhancement
- Dominant language
- Vim Script
- Stars
- 159
- Forks
- 18
- PR merge metrics
- No merged PRs in 30d
Description
_From @trotzig on March 3, 2016 17:35_
As suggested by @wincent in https://github.com/trotzig/import-js/pull/206
> Might also want to use mappings moving forward, as those are considered a little more useful: http://whileimautomaton.net/2008/09/27022735
_Copied from original issue: Galooshi/import-js#209_
Contributor guide
Research direction
Start by reading PR #206 and the linked discussion of mappings to understand the requested direction. Identify which mappings in vim-import-js are in scope, then define the expected mapping behavior and verify that the resulting mappings match that decision.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- vim
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100