standard way include plugin as a dependency of another plugin
Hi I'm writing a plugin and want it to depend on another plugin installed. At the moment I just have a line source in my plugin that pulls in that plugin. Is there a standard way of doing this or do plugin authors just invent their own way? Could I use Vundle here instead? -- -- You received this message from the "vim_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: gerrit code review
Anyone have any experience performing gerrit code reviews from vim? I wrote plugin for that task: https://github.com/stargrave/gerrvim You open necessary commits through the fugitive, visually select lines you want to comment, enters \cc and type in the comment in appeared separate window. All comments are aggregated in temporary file that is converted to JSON (separate simple Perl utility) and submitted to Gerrit server making the review change. Also there is utility for downloading review comments to simple text file, allowing answering on them without any awful web-interface: only Vim, ssh/curl and that plugin (with additional two scripts). -- Happy hacking, Sergey Matveev Thank you. I will try it. -- -- You received this message from the vim_use maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups vim_use group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: clang_complete and objective c
Well I answered my own question. Basically setting the following
let g:clang_user_options='-fblocks -isysroot /Developer/Platforms/
iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator4.3.sdk -
D__IPHONE_OS_VERSION_MIN_REQUIRED=40300'
in my vimrc file seems to do convince clang that the code is ok
enough for code completion to work.
On Jul 10, 1:18 am, sash...@gmail.com sash...@gmail.com wrote:
Hi
I've been trying to get the clang_complete plugin to work with
objective c code for iOS. It works for C++ code which means that it's
installed right. However when it comes to objective-c code that is
intended to run on iOS it fails. For example this code here:
#import UIKit/UIKit.h
int main(int argc, char *argv[])
{
NSAutoreleasePool *pool = [[NSAutoreleasePool alloc] init];
int retVal = UIApplicationMain(argc, argv, nil, nil);
[pool release];
return retVal;
}
Fails with:
UIKit/UIKit.h file not found
when I try to invoke autocompletion on an entity with a 'dot' e.g.
typing 'pool.'
I can compile it on the command line successfully with the following
command:
clang -isysroot /Developer/Platforms/iPhoneSimulator.platform/
Developer/SDKs/iPhoneSimulator4.3.sdk -
D__IPHONE_OS_VERSION_MIN_REQUIRED=40300 -c main.m
So I assume somehow I have to tell clang_complete to use the
parameters above in addition to what it already knows. How do I do
that?
Thanks
--
You received this message from the vim_use maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
clang_complete and objective c
Hi
I've been trying to get the clang_complete plugin to work with
objective c code for iOS. It works for C++ code which means that it's
installed right. However when it comes to objective-c code that is
intended to run on iOS it fails. For example this code here:
#import UIKit/UIKit.h
int main(int argc, char *argv[])
{
NSAutoreleasePool *pool = [[NSAutoreleasePool alloc] init];
int retVal = UIApplicationMain(argc, argv, nil, nil);
[pool release];
return retVal;
}
Fails with:
UIKit/UIKit.h file not found
when I try to invoke autocompletion on an entity with a 'dot' e.g.
typing 'pool.'
I can compile it on the command line successfully with the following
command:
clang -isysroot /Developer/Platforms/iPhoneSimulator.platform/
Developer/SDKs/iPhoneSimulator4.3.sdk -
D__IPHONE_OS_VERSION_MIN_REQUIRED=40300 -c main.m
So I assume somehow I have to tell clang_complete to use the
parameters above in addition to what it already knows. How do I do
that?
Thanks
--
You received this message from the vim_use maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
Re: Text wrapping with gq is doing something really weird ...
Hey thanks I was having the same issue. On Feb 12, 10:12 am, Ben Fritz fritzophre...@gmail.com wrote: On Feb 11, 3:00 pm, Joyce Tipping jo...@spencertipping.com wrote: Hi guys, I've been having an odd problem with my automatic text wrapping in vim. I wrap my text with the gq command, sometimes as gqap (to wrap a paragraph), sometimes as gggqG (to wrap the whole document). I've been using vim for years and I don't recall ever having this issue. Just recently, it started doing something really weird. I think a picture is worth a thousand words, so here's a blog post I've been working on: http://old.nabble.com/file/p27554664/vim-problem.png Here's the contents of my vimrc: [snip] 7 set smartindent Assuming I understand your problem, this is the cause. I presume the strange behavior you're referring to, is the lines after the line that starts with for a car The 'smartindent' option is a deprecated option for indenting C code. The C programming language has a construct called a for loop which is (generally) a line that begins with the word, for and is indented on the next line. 'smartindent' is not really meant for plain text editing, and you generally get better results for C code by turning on filetype indentation with filetype indent plugin on in your .vimrc. My recommendation: remove 'smartindent' from your .vimrc and consider enabling filetype plugins and indentation.- Hide quoted text - - Show quoted text - -- You received this message from the vim_use maillist. For more information, visit http://www.vim.org/maillist.php
