The Wayback Machine - https://web.archive.org/web/20201125222549/https://github.com/technicalpickles/pickled-vim
Skip to content
master
Go to file
Code

Latest commit

 

Git stats

Files

Permalink
Failed to load latest commit information.
Type
Name
Latest commit message
Commit time
 
 
 
 
 
 
vim
 
 
 
 
 
 
 
 

README.markdown

pickled-vim

These are the vim configurations I'm using. I'll try to comment as much as I can about what's going on, but your mileage may vary.

Principals

  • optimize for macOS and MacVim, but work with regular vim on macOS and elsewhere
  • optimize for Ruby, Python, Javascript, and shell development
  • try to balance minimalism and full featured but bloated
  • keep reasonably up-to-date
  • mimic common idioms/commands/behaviors from other editors when they are useful
    • ie command-t for fuzzy finding in TextMate and Atom
  • lay the groundwork for maybe switching to neovim someday

Installation

This repository uses scripts to rule them all. To setup:

script/setup

If you are on macOS, you are done. If you are on another platform, you'll need to figure out how to install the following:

Fonts (only needed for gui):

Dependencies:

Updating

Just run script/setup again, which would pull down any new dependencies.

Usage

Just vim as usual, more or less.

Filetype specific features

I use syntastic for a few filetypes, which depend on external checkers. Different projects will use different versions of languages and tools (ie with rbenv, nodenv, etc), so sometimes the current project won't have those. To fix missing checkers, I have some helper scripts. Call them from your current directory where you are missing checkers

  • coffeescript: path/to/pickled-vim/script/bootstrap-coffee
  • python: path/to/pickled-vim/script/bootstrap-python

Neovim

Depending on your current python or ruby, you may need to reinstall some packages. Similar to above:

path/to/pickled-vim/script/bootstrap-neovim

After that :checkHealth should confirm everything clear.

Development

For debugging mappings not working as expected:

  • use map (or whichever variation) with nothing to map to find what its doing, ie map <C-]>
  • if it's mapped to a function, grep .vim for that
  • if it's a specific plugin, check the source/docs to see if there's an option to disable

About

My personal VIM configurations

Resources

Releases

No releases published

Packages

No packages published
You can’t perform that action at this time.