Also, works on GNU/Linux and Windows. Also, free software. Also, I'm the co-author.
I know the whole point of Dash is to have locally cached, offline documentation copies, but I was thinking it would be amazing to use that to feed Helm candidates, but actually open the real, live documentation page.
It seems there are some docsets already doing that[1]. Creating your own docsets is dead easy. just a simple sqlite3 file with a single table.
You can find an example I hacked myself here[2] (very hackish).
It's basically creating a table:
create table searchIndex(id INTEGER PRIMARY KEY, name TEXT, type TEXT, path TEXT);
CREATE UNIQUE INDEX anchr ON searchIndex (name, type, path);
And filling it with data: insert into searchIndex(name,type,path) VALUES ('foo','function','https://example.com')
[1]. https://github.com/areina/helm-dash/issues/65 .The helm-dash repo tagline on GitHub says "Browse Dash docsets inside emacs", so I quickly dismissed it as I don't use Mac.
Reading a bit further, now I see that it doesn't need Dash to be installed. So that's great! I'll see if an ivy/counsel version is out there.
Yep, helm-dash can download docsets from dash servers and use them without the need of Dash whatsoever.
https://github.com/nathankot/counsel-dash .
Enjoy!
There are a few main things that will probably keep me on Dash, for the time being. In no particular order:
1. Global shortcut - Being able to quickly show-search-hide from anywhere is extremely useful for me. I can quickly refresh myself on the syntax of an uncommon function. The faster I can do that, the less likely I am to break my flow.
2. Support for random/obscure projects - On top of community-added docs, Dash lets you point it at any random GitHub project and it will pull down the README. This has come in handy plenty of times for me when using small tools and components. Sure, it's not as nice as full documentation, but it's nice having that README searchable in the same place and offline (see reason #1).
3. Docsets - Dash lets you define groups of frameworks (etc.) and name them. You can even specify which version of a framework to use in the docset. This allows me to tailor my results to a particular stack, depending on which project I'm currently working on.
EDIT: I should read :)
http://www.loopinsight.com/2016/10/10/apple-responds-to-dash...
[1] https://blog.kapeli.com/dash-for-ios-back-on-the-app-store
They’re allegations, sure. I said that in my second comment. But Tom didn’t hedge his words there.
Publishing the phone call was kinda dumb, yeah, but it's still pretty far from "engaging in unethical practices". It seems more like a guy feeling cornered, acting under pressure and making bad decisions.
In any case, it's water long under the bridge now, and Dash is an excellent app used my many developers (including within Apple). Trying to poison the well is in pretty bad taste.
Facts not up for debate: the developer of Dash enrolled two accounts in the ADP with the same credit card, and these accounts shared at least one test device. One of these accounts participated in obvious fraudulent activity.
Unfortunately, nobody is around to corroborate Bogdan's side of the story. As far as we know, Bogdan made up his supposed relative/friend (ala "I didn't send that embarrassing text to my crush - it was my asshole friend!") to escape blame. And even if his side of the story is true, how is he not partially culpable for the fraud? By enrolling an account with his credit card and giving it to someone else, he enabled them to commit fraud on the App Store. If I buy a gun and give it to my brother and he shoots someone, am I not partially responsible for that outcome?
It's not quite damning enough for me to not use Dash, but it doesn't exactly give me faith in Dash's developer either.
Disclaimer: I'm the maintainer of DevDocs
As a long-time dash user in the past, devdocs felt like home and just works nicely and without any unnecessary features.
For what it’s worth on Linux the open source alternative is Zeal