From 97d34b559bda1bf76cff74ee69111d0c61bd7a8e Mon Sep 17 00:00:00 2001 From: Vinay Shankar Shukla Date: Thu, 12 Mar 2020 14:01:55 +0530 Subject: [PATCH] Fix markdown formatting for README --- README.md | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/README.md b/README.md index e664c0d..dbf617c 100644 --- a/README.md +++ b/README.md @@ -1,4 +1,4 @@ -#Notice +# Notice This project is being replaced with [OmniSharp Roslyn](https://github.com/OmniSharp/omnisharp-roslyn). I'll still accept PRs for this project, but please note that all development has stopped here. @@ -13,9 +13,10 @@ HTTP wrapper around [NRefactory] (https://github.com/icsharpcode/NRefactory) all This is the server component for the [Vim OmniSharp plugin](https://github.com/nosami/OmniSharp), [YouCompleteMe](https://github.com/Valloric/YouCompleteMe), [Sublime Text 2](https://github.com/PaulCampbell/OmniSharpSublimePlugin), [Sublime Text 3](https://github.com/moonrabbit/OmniSharpSublime), [Emacs OmniSharp plugin](https://github.com/sp3ctum/omnisharp-emacs) and [Atom plugin](https://github.com/Mpdreamz/atom-sharper) -#Build +# Build + +#### OSX / Linux -####OSX / Linux Requires a minimum of Mono 3.0.12 - If you absolutely must use mono 2.10 then checkout the mono-2.10.8 tag. [Updating mono on ubuntu](https://github.com/nosami/OmniSharpServer/wiki). If you are using OSX, please use the official version of Mono as the homebrew version has [known](https://github.com/nosami/OmniSharpServer/issues/83) [issues](https://github.com/nosami/OmniSharpServer/issues/80). ``` git clone https://github.com/OmniSharp/omnisharp-server.git @@ -24,7 +25,7 @@ Requires a minimum of Mono 3.0.12 - If you absolutely must use mono 2.10 then ch xbuild ``` -####Windows +#### Windows ``` git clone https://github.com/OmniSharp/omnisharp-server.git cd omnisharp-server @@ -52,7 +53,7 @@ To start the Omnisharp server manually (The Vim OmniSharp client and YouComplete [mono] OmniSharp.exe -s path ``` -###Problems (or just want to see what's going on)? +### Problems (or just want to see what's going on)? Try adding an extra ```-v Verbose``` to the end of the command line. You should see something like the following.