Eric Milford

@eidge Were you able to get a setup you're happy with for importing and viewing Hexdocs in `dasht`? I'm just starting down that path and came across this issue. Thanks.

Thanks. Downloading and extracting the docsets directly from hex.pm didn't work because of the directory structure format, sqlite, etc. required by dash. I've found that downloading the docsets via Dash...

Here's an example https://repo.hex.pm/docs/ecto-2.0.4.tar.gz There's a good chance I borked something when using `dasht-docsets-extract`. 😁

I haven't had a chance to look at it or to give it a shot, but came across [this](https://github.com/yesmeck/hexdocset) which might help.

There's seemingly something to do with hexdocset when downloading a hex docset within Dash. It's from a different app; the one you linked to I'd need to spend more time...

@ljohnston Are you receiving an error by chance? I'm not sure if this is related to your issue, but I'm also recently seeing odd save behavior. I'm getting the error...

@otavioschwanck I have the same `keymaps` as you, and similarly they no longer work. By any chance that you're seeing file read errors if you run `:file` after opening a...

@npezza93 reverting the [Ruby queries changes](https://github.com/nvim-treesitter/nvim-treesitter-textobjects/pull/247) fixes the read errors issue mentioned in my previous comment. I can look into it more tomorrow, but any idea what's going on or...

@npezza93 Yes, I've pulled the latest from nvim-treesitter. When you ask whether I've installed the newest ruby-tree-sitter, do you mean the latest Ruby parsers? If so, `TSUpdate` show that all...

Looks like this was an issue on my end. Some combination of reinstalling plugins, parsers, etc., to resolve some checkhealth errors seems to have everything working again for me. Thanks!