Add instructions for starting an OmniSharpServer process to README
Merge branch 'develop'
Recommend using native curl client on Windows systems

We had a probled related to a cygwin curl being installed here:
https://github.com/sp3ctum/omnisharp-emacs/issues/75

The issue was resolved by using a Windows native curl.
Merge branch 'develop'
Add howto for setting up the OmniSharp server in a Cygwin environment
Start Omnisharp from Emacs and inside Emacs
fixed variable-/function-names and indentation
Remove omnisharp--filter-company-candidate

One of the completions being equal to the prefix is usually normal, and
removing it in the backend means idle completion will always try to
suggest completing to something, even if the current text is valid in
the current context.

If removing completions like this is somehow beneficial, it's probably
better performed in `company-transformers`.
company-omnisharp: use `annotation' instead of `crop'

Make use of text properties, they are handy for carrying extra
information.

`omnisharp--make-company-completion' still looks a bit suboptimal
(ideally, annotations would only be calculated when they're
displayed), but omnisharp doesn't seem to return huge completion lists
anyway.

Support for `crop' will be removed in company-mode 0.8, so this kind
of change is sort of mandatory.
Do some reformatting
Drop the auto-complete dependency

The popup.el dependency remains harder to cut out (for example,
`omnisharp-auto-complete-popup-keymap' references `popup-menu-keymap'
in its initvalue form).
Update the README
Add prompt for omnisharp-start-omnisharp-server
Allow starting OmniSharpServer via the graphical menu
Whitespace fixes
Document starting OmniSharpServer in emacs in README.md
Merge branch 'github-mgutekunst-master' into develop

This merge provides initial support for starting and managing an
OmniSharpServer instance inside emacs.
Fix message capitalization
Fix not caching OmniSharpServer path to correct variable

This could potentially fail, in, uh, some cases.
What.
Style changes

Setq returns the set value, so no need to use progn to group expressions
together.
Since if has no "else" expression, we should use (when)