All Projects → keith → Investigate.vim

keith / Investigate.vim

Licence: mit
A Vim plugin for looking up documentation

Projects that are alternatives of or similar to Investigate.vim

Naturaldocs
Natural Docs source code documentation system
Stars: ✭ 106 (-62.41%)
Mutual labels:  documentation, documentation-tool
Gdscript Docs Maker
Create documentation and class references from your Godot GDScript code
Stars: ✭ 121 (-57.09%)
Mutual labels:  documentation, documentation-tool
Pasdoc
Documentation tool for ObjectPascal (Free Pascal, Lazarus, Delphi) source code
Stars: ✭ 110 (-60.99%)
Mutual labels:  documentation, documentation-tool
Community
Modern Confluence alternative designed for internal & external docs, built with Golang + EmberJS
Stars: ✭ 1,286 (+356.03%)
Mutual labels:  documentation, documentation-tool
Hippie Swagger
API testing tool with automatic swagger assertions
Stars: ✭ 166 (-41.13%)
Mutual labels:  documentation, documentation-tool
Docpht
With DocPHT you can take notes and quickly document anything and without the use of any database.
Stars: ✭ 90 (-68.09%)
Mutual labels:  documentation, documentation-tool
Lurker
📖 The ultimate tool for documenting and testing APIs in Rails
Stars: ✭ 120 (-57.45%)
Mutual labels:  documentation, documentation-tool
Graphdoc
Static page generator for documenting GraphQL Schema
Stars: ✭ 1,218 (+331.91%)
Mutual labels:  documentation, documentation-tool
Simpler Paper
elegant document generation tool.
Stars: ✭ 151 (-46.45%)
Mutual labels:  documentation, documentation-tool
Awesome Documentation Tools
🔥 📚 All the tools, processes and resources you need to create an awesome API & Project documentation
Stars: ✭ 138 (-51.06%)
Mutual labels:  documentation, documentation-tool
Drf Autodocs
Ultimately automated DRF documentation rendering(UNMAINTAINED)
Stars: ✭ 82 (-70.92%)
Mutual labels:  documentation, documentation-tool
Devdocs Macos
An unofficial DevDocs API Documentation viewer for macOS.
Stars: ✭ 258 (-8.51%)
Mutual labels:  documentation, documentation-tool
Rocannon
Vim for Ansible playbooks: omni-completion, abbreviations, syntax, folding, K-docs, and colorscheme
Stars: ✭ 80 (-71.63%)
Mutual labels:  documentation, viml
Jekyll Rtd Theme
Just another documentation theme compatible with GitHub Pages
Stars: ✭ 92 (-67.38%)
Mutual labels:  documentation, documentation-tool
Vim Plugin Viewdoc
Vim plugin: flexible viewer for any documentation
Stars: ✭ 79 (-71.99%)
Mutual labels:  documentation, viml
Catalog
Create living style guides using Markdown or React
Stars: ✭ 1,527 (+441.49%)
Mutual labels:  documentation, documentation-tool
Zeal
Offline documentation browser inspired by Dash
Stars: ✭ 9,164 (+3149.65%)
Mutual labels:  documentation, documentation-tool
Jsdoc To Markdown
Generate markdown documentation from jsdoc-annotated javascript
Stars: ✭ 1,199 (+325.18%)
Mutual labels:  documentation, documentation-tool
Documentalist
📝 A sort-of-static site generator optimized for living documentation of software projects
Stars: ✭ 130 (-53.9%)
Mutual labels:  documentation, documentation-tool
Hexo Theme Doc
A documentation theme for the Hexo blog framework
Stars: ✭ 222 (-21.28%)
Mutual labels:  documentation, documentation-tool

investigate.vim

A plugin for looking documentation on the word under the cursor. You can choose to open it in a browser, with Dash on OS X, or with an arbitrary shell command.

Example

Web

Setup

By default investigate is mapped to gK. If you want to set up your own mapping you should use something like this:

nnoremap <leader>K :call investigate#Investigate('n')<CR>
vnoremap <leader>K :call investigate#Investigate('v')<CR>

With this mapping, using K when your cursor is on a specific word will open its documentation. The help file has tons of documentation on configuration. Here are some of the basic options.

Configuration

Dash

If you want to open everything in Dash you need to set:

let g:investigate_use_dash=1

This value is ignored unless you're on OS X. If you want to use Dash conditionally based off the current filetype you can set something like:

let g:investigate_use_dash_for_ruby=1

If you want to use something else, like a URL for a single type you'd want to use this which will override the global Dash setting:

let g:investigate_use_url_for_ruby=1

If you want to use a different keyword in Dash for a given language you can set it by using:

let g:investigate_dash_for_ruby="rails"

This would set all Ruby files to open in the Rails documentation. Note: If you're using a Dash 1.9.3 or newer you don't have to set this for docsets that you have renamed.

URLs

If you don't like the website I chose as the default for a filetype you can redefine it with:

let g:investigate_url_for_ruby="http://ruby-doc.com/search.html?q=^s"

Where ^s will be replaced with the word under the cursor for Ruby files.

Custom Commands

You can also open documentation with arbitrary shell commands. See investigate-writing-commands in the documentation for more info.

Project specific settings

You can setup project specific settings with an .invrc file from the directory you launch Vim in. For example for a Rails project you may want to set Ruby files to open Rails documentation for that single project but not other Ruby gem based projects you're working on. To do that the file would look something like this:

[syntax]
ruby=rails

This will set a syntax variable:

let g:investigate_syntax_for_ruby=rails

Which entirely changes Ruby files to open in the Rails documentation. See investigate-conf-file for more information.

If you don't have a preferred installation method check out vim-plug

Development

If you find any bugs, want any languages added, or want any default language settings changed, please submit an issue.

Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].