This is my first post in this blog. I want to start here my adventure as blogger. What I want to talk about is a list of trick I used in my first contribute to a vim plugin. Plugin is stored here: vim-php/vim-composer. It aims to manage composer directly from vim. It already comes with many features, when I decided to add my personal one. Php developers, often use composer, and composer auto-generate files and know all file path. Instead of use the slowet ctag, or CtrlP, ... why dont ask to composer where files are?
How to get current word in VimL
I must thanks stackoverflow for this. There are several ways to take word under the cursor in Vim. expand('<cword>') i used in this little script.
How to get the output of a bash command, from vim
Oh! This is very nice. In VimL we can execute a command in bash, and get the output. When I discovered that with a grep and some awk is possible to get the position of a particular class, I've build my command to ask to composer a particular class path. That's great!
How to show a message in vim
Finally, the third think I've learned, is the way to show message in the command line. In this case, my grep/awk command can find more or less file. When grep results in more or less than one item, ... I wanted to tell users that there are not unique file in composer auto-generated file. "echo" is the command
Pay attention to readme file
Pay more and more attention to README file if you want to contribute to an open source project. User should know what you have done, reading readme file. README is automatically displayed in github project. Care about it because it must contains all information that your users should know to work with your code.
In some open source projet, also exists a CONTRIBUTING files. This files contains all information for developers that onw to contribute to a project. Coding standard, test informations, suggestions about rebasing and commit message.