61–70 of 84 posts
Edit: I was being stupid, the home page just didn't load the first couple of times I tried.
Sourcegraph CEO here. Thanks for posting! Our new VS Code-based UI makes Sourcegraph a better way for you to read a codebase on the web with the full power and intelligence of an editor, without the hassle of cloning or configuration. It provides jump-to-def, hovers, find references, advanced search, symbol search, cross-repo references, etc., for any repo and any commit on GitHub (in Go, Java, and some other languag…
Looking at a file from one of my repos, the syntax highlighting looks wonky. https://sourcegraph.com/github.com/eriknstr/VoxelMode-2.5D/-... Everything on every line after '#' on line 21 is the same save for backslashes and ":3" which are blue.
Earlier quoted context omitted.
Sourcegraph CEO here. We have a Firefox extension at https://addons.mozilla.org/en-US/firefox/addon/sourcegraph-a... , but it does not have quite as many features as the Chrome one. I agree we should open-source the browser extension code, though. I would like us to do that soon. Can you send me a quick email at sqs@sourcegraph.com so I can tell you when it's open source?
It says "Compatible with Firefox 57+" so I assume it's based on the same code as the Chrome one… What APIs do you use that are not supported in Firefox? :) (Also it says "Released under MIT/X11 License" already…)
Regarding the licensing, I meant that we'll release the build scripts and supporting libraries used to build it, not just the final bundle.
Earlier quoted context omitted.
Looking at a file from one of my repos, the syntax highlighting looks wonky. https://sourcegraph.com/github.com/eriknstr/VoxelMode-2.5D/-... Everything on every line after '#' on line 21 is the same save for backslashes and ":3" which are blue.
We're working on improving that, and it'll work well for Python when we officially support Python. See https://news.ycombinator.com/item?id=14261611 for why, if you're curious.
Sourcegraph CEO here. Thanks for posting! Our new VS Code-based UI makes Sourcegraph a better way for you to read a codebase on the web with the full power and intelligence of an editor, without the hassle of cloning or configuration. It provides jump-to-def, hovers, find references, advanced search, symbol search, cross-repo references, etc., for any repo and any commit on GitHub (in Go, Java, and some other languag…
Your site is sorely lacking a good FAQ though. I just spent 10 minutes trying to figure out what languages you support, looking for a roadmap, trying to figure out if I can use this with any random repo on GitHub, and with which pricing plan. I only got the answers when I looked at the HN comments.
Sourcegraph CEO here. Thanks for posting! Our new VS Code-based UI makes Sourcegraph a better way for you to read a codebase on the web with the full power and intelligence of an editor, without the hassle of cloning or configuration. It provides jump-to-def, hovers, find references, advanced search, symbol search, cross-repo references, etc., for any repo and any commit on GitHub (in Go, Java, and some other languag…
The product looks super useful, thanks for your efforts and congrats! Your site is sorely lacking a good FAQ though. I just spent 10 minutes trying to figure out what languages you support, looking for a roadmap, trying to figure out if I can use this with any random repo on GitHub, and with which pricing plan. I only got the answers when I looked at the HN comments.
Syntax highlighting is laughably bad The "int" in "maintained" is highlighted in checkup_test.go as a type
Sourcegraph CEO here. There are indeed some glitches in syntax highlighting, on other languages as well. I hope it doesn't significantly detract from the product value, but I understand it is not good. Here's why it's happening: We're using TextMate syntax bundles, which require the Oniguruma regexp engine, which only has partial pure-JavaScript implementations that can run in the browser. We use https://github.com/b…
VS Code offers pretty decent Monarch syntax definitions in the monaco-languages at [4]; you're probably better off just using those instead.
[1] https://microsoft.github.io/monaco-editor/index.html [2] https://microsoft.github.io/monaco-editor/monarch.html [3] https://github.com/Microsoft/monaco-editor [4] https://github.com/Microsoft/monaco-languages/tree/master/sr...
developing in the browser, especially at large organisations is a huge productivity benefit in addition to cost benefit etc. the pros are endless. just let your mind wonder.
intro -----
the one i worked on, alongside Sourcegraph is available at:
live: https://cloud.bana.io/monaco-go/ repo: https://github.com/mbana/monaco-go
the backend was adjusted somewhat to support a WebSocket connection, besides that, the code was almost written entirely by the folks over at Sourcegraph. please note i do not have funds to pay for the Azure cloud so it might be down, or seem very slow.
i would love to resume development on this seeing as i work at large organisation and i see the huge potentional.
implementation --------------
in my opinion, i think the approach taken in my implementation might be better. there was hardly any custom code aside from stubbing code out to make VScode, or rather, monaco-editor run in the browser.
i will stress, i can and want to continue finishing this and having it land in monaco-editor master but my current job doesn't allow it.
if anyone wants to join me, please do say.