I would like to add pythonhelper to vim-powerline, using MacVim.
There is an issue that discusses this on github, but although the issue is closed the resolution was not clear.
What is the best way to go about doing this?
Related
This question already has answers here:
Identify which vim plugin is causing behavior
(2 answers)
Is there a "vim runtime log"?
(6 answers)
Closed 8 months ago.
I just installed the dotfiles from this repo: https://github.com/skwp/dotfiles
When I try to save one of my javascript file a lint section appears. However I don't know which plugin it's coming from:
Is there a way to find out where this is coming from? I tried deleting a plugin that I thought was responsible but it's just trial and error. Is there a more systematic way?
Short answer
That feature is provided by a plugin called Syntastic, itself a third-party wrapper around built-in features (:help :make, :help quickfix), themselves using external programs (most likely eslint). You should must read the documentation of that plugin: :help syntastic.
Long answer
The whole point of customization is to adjust your environment to your needs. This is done by:
identifying your needs/problems,
looking for solutions that don't create more needs/problems,
putting them in practice.
By downloading someone else's config you essentially gave up before the first step. Your environment is now adjusted to someone else's needs and is full of settings and plugins you may or may not need, that may or may not suit your needs. You willingly chose to install a black box you don't understand instead of actually learning your editor and configuring your environment to suit your needs.
You wanted a quick install and you get an impenetrable mess. I'd suggest you get rid of all that crap ASAP.
Lack of curiosity will get you nowhere, especially in programming.
Would someone be kind enough to show me what exact code is needed in the _vimrc file to get the Python-mode plugin to work! Thanks! (I also read that it is out-dated) is the Jedi plugin that much better? Thanks from the VIM newbie!!!
Bob
You won't be lucky if you expect a single command in your virmrc. Turning vim into a python ide is a collection of multiple plugins you can either manage by hand or use a plugin manager like vundle. Best practice is to use your configuration along with a repository hosted for example on github using git. You can use mercurial or baazar just as well.
Walking through one of the numerous tutorials on the net will be your only chance.
For example here: https://github.com/mbrochh/vim-as-a-python-ide along with the video:
https://www.youtube.com/watch?v=YhqsjUUHj6g
Does anyone know some shortcuts for FakeVim to change between files?
Is it possible to use buffers in Fake Vim? I accidentally found out that Ctrl+w,w gets you the next window. Does anyone know other? For example getting to the left, right, top, bottom windows?(vim's Ctrl+w,l and others)? Is there any documentation on FakeVim? Is it possible to configure FakeVim's vimrc file to create shortcuts for changing between buffers and the Projects view?
Thanks!
Recently I've been doing most of the changes on FakeVim plugin.
You can find list of Vim commands supported by FakeVim at https://github.com/hluk/FakeVim (recent version from Git master branch).
I'm still not sure how to document the features in Qt Creator. I'll probably implement something like :help <command> in near future.
The FakeVim documentation is severely lacking. This paragraph, for example, is so fuzzy it's borderline irresponsible:
In the FakeVim mode, most keystrokes in the main editor will be intercepted and interpreted in a way that resembles Vim. Documentation for Vim is not included in Qt Creator. For more information on using Vim, see Documentation on the Vim web site.
Basically, without a proper documentation or a look at the editor's source code it's impossible to know what should work, what shouldn't and in which way the behavior of what works deviates from Vim's behavior. And that's what passes for a modern IDE, these days.
Whatever…
I think that your best bet is simply trial and error: since you appear to know how to use Vim you'll have a lot of commands and shortcuts to try.
I have found this resource for Ruby/Rails snippets, seems like it has lots of cool snippets that I could use with vim.
But since I'm new to vim, I don't know how to enable those snippets to my vim editor. There is no instruction manual as such.
How can I get these kind of snippets enabled in the vim editor?
Those snippets are for the snipMate - TextMate-style snippets for Vim plugin. You need to install it first.
Note that though this plugin isn't maintained any more, it's still working fine (and probably will continue to do so, due to Vim's great record of backwards compatibility), and is still used by many people (me included). There's a renewed fork available, though: garbas/vim-snipmate. A newer, more powerful plugin is UltiSnips - The ultimate snippet solution for python enabled Vim, which can convert the old snipMate snippets into its format. So, there's a lot of choice.
About Snippet Plugin in Vim
I recommend the plugin Neosnippets: https://github.com/Shougo/neosnippet This is the best in my opinion.
Step 1: Install plugin. Recommend using Pathogen to install
step 2: Download/clone a snippet repo you like to local machine, or create your own(recommeneded)
Step 3: Set the path of above repo as Neosnippets's snippets folder in vimrc
let g:neosnippet#snippets_directory='~/path/to/above/snippets/'
Step 4: Customize more if you like, according to the help file.
For the repo you mentioned
I checked it.
One problem is it's out of date, many Rails code are several years ago. They are of little use now.
The other problem is the format is not compatible with NeoSnippet. You can check :help neosnippet-snippet-syntax for how to write snippets for NeoSnippets. It's simple while easy to use.
When i try to write import org.junit.Test, just when I have completed writing import.jun it converts(auto-completes) it to import org.jun=acp#onPopupPost().
Is it some eclim autocomplete feature which is misbehaving or something else? I only face this issue when I am inside a project opened via eclim. Other wise there is no issue.
Looks like you have a problem with the AutoComplPop plugin; part of its mapping is inserted literally. I'm using the plugin myself, but haven't seen that issue. It may be interference with another plugin; have you done any updates to other plugins recently?! If you can reproduce the problem with a clean .vimrc and no other plugins loaded, submit an issue to the author.
To temporarily disable the plugin (without uninstalling), put the following into your ~/.vimrc:
let g:loaded_acp = 1