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.
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.
This doesn't work either https://sourcegraph.com/github.com/rails/rails :(
Would be great if it worked, I liked the example with Go code.
As you can imagine, Ruby code intelligence (type inference, etc.) is super tough, and there are maybe 5-10 people in the world who could build it right now. We'd love to find and sponsor a Ruby expert to add Ruby support to Sourcegraph. If you know of anybody, please send them my way ([email protected]).
Is Yin Wang in the list?
I remember reading something about it, but now only search engines retain traces of it.
Too bad it's in Chinese, but Google Translate got me the gist. An unfortunate story.
Not sure why he didn't settle on GPL or AGPL, though.
Disclaimer: I contributed to rubocop.
Here are some libraries that could contain that one-in-a-billion knowledge:
- RDL: type annotation, but also has a static type checker. https://github.com/plum-umd/rdl#static-type-checking
- Typed: gradual typing system, with type inference https://github.com/antoniogarrote/typed.rb
- Jetbrains has something, too: https://github.com/JetBrains/ruby-type-inference
I'm familiar with those projects, but when I last tried them, they did not work well enough with some additional constraints that the nature of our product imposes (chiefly requirements for error-tolerance and cross-project resolution), and we weren't able to find people to help us. I will try them again and see if we can sponsor someone now to help integrate when with Sourcegraph, since it looks like quite a bit of progress has been made in the last few months.
Is it possible to use something to make this work?
https://gist.github.com/sqs/2a2680eff4dad159ae754756fe9326c2
Mobile experience seems poor:
- Weird margins taking up lots of the screen
- Back button seems to be disabled (I pressed it about 200x trying to get back to HN and nothing happened)
- "view mode" would be nice: don't pop up keyboard for editing when I click on some part of a source file, but still support clicking symbols and offering options e.g. jump to definition.
You can however set up your own keybindings by editing the keyboard shortcut settings. Open the Quick Open (on a Mac, Command+Shift+P or F1 on a PC), and type "Open Keyboard Shortcuts". From here you can configure any mappings you'd like.
If you find yourself reading code on GitHub a lot, or cloning repos to open and read in your editor, you'll find Sourcegraph useful. If not, then you probably won't find it useful yet, but you might like our Chrome extension, which adds these features inline on GitHub.com (https://chrome.google.com/webstore/detail/sourcegraph-for-gi...).
We'd love feedback. Try hovering over some tokens at https://sourcegraph.com/github.com/sourcegraph/checkup@maste..., for example. Click on the smiley in the bottom right to give feedback.
Huge thanks to the VS Code team for building an amazing and extensible open-source code editor that we can build on.