* documentation: copied old documentation from wiki
* command: better online documentation
Help without arguments prints just a short summary for each command,
help followed by a command prints the command's syntax and a longer
explanation.
* documentation: automatically generate Documentation/cli/README.md
* documentation: headless invocation should specify --api-version=2
* documentation: More API documentation
* documentation: copied documentation from client.go to rpc2/server.go
Fixes#164
New API version with better backwards compatibility plus mechanism to
select the API version that a headless instance should use.
Adds service/test/cmd/typecheckrpc.go to type check the RPC interface.
I ran through these instructions and didn't notice that the
certificate I'd created appeared three times in the list I
was looking at. Emphasize where the trust setting is
enabled.
Going forward, all documentation should be placed in the Documentation
directory in the root of the project. This switch allows maintainers to
approve updates to documentation before they are committed, as opposed
to the pre-existing wiki which anybody could modify.
Currently the Documentation directory includes docs on building, usage,
and minimal docs around the API. This is just the initial commit, and
documentation will continue to improve over time.
Some changes have been made (and will continue to be made) to `cmd/dlv` to
ensure we can auto-generate documentation for all commands from the
newly provided script `scripts/gen-usage-docs.go`, which can be invoked
via `go run scripts/gen-usage-docs.go`.
Additionally, version has been split into its own package. This was a
bit of housekeeping related to the changes made the `cmd/dlv`.
