Aaron Schrab
fc22af0d1e
Use classes for managing vim interaction
Create classes for interacting with vim, a base class with common methods, a class for interacting via screen, and one for interacting on Windows. At startup time an instance of one of these classes is created, and that object is passed to all of the tests instead of the session. I haven't been able to get UltiSnips working in vim on Windows to really test this, but I have verified that vim interactions still work.
UltiSnips ========= This is the official repository for UltiSnips on GitHub. It is held in sync with the official bzr repository over at Launchpad [1] and is meant as a convenience for contributors. Send Pull request to this repository, not the automatic clone from vim-scripts. Note that we do not use the Issue tracker here one GitHub because the one on Launchpad is superior and already has a significant history. Please report `issues over there`_. [1] http://launchpad.net/ultisnips .. _issues over there: https://bugs.launchpad.net/ultisnips Screencasts ----------- The blog posts of the screencasts contain more advanced examples of the things discussed in the video. * `Episode 1: What are snippets and do I need them?`__ * `Episode 2: Creating Basic Snippets`__ * `Episode 3: What's new in version 2.0`__ * `Episode 4: Python Interpolation`__ __ http://www.sirver.net/blog/2011/12/30/first-episode-of-ultisnips-screencast/ __ http://www.sirver.net/blog/2012/01/08/second-episode-of-ultisnips-screencast/ __ http://www.sirver.net/blog/2012/02/05/third-episode-of-ultisnips-screencast/ __ http://www.sirver.net/blog/2012/03/31/fourth-episode-of-ultisnips-screencast/
Description
Languages
Python
91.9%
Vim script
7.3%
Makefile
0.4%
Shell
0.3%
Dockerfile
0.1%