blob: 465905873c10ad624e49a91df2efd0e5801e039a [file] [log] [blame] [view]
Rebecca Stambler96954832019-09-15 20:25:54 -04001# Command line
2
Rebecca Stamblerd78b04b2020-12-28 13:26:14 -05003**Note: The `gopls` command-line is still experimental and subject to change at any point.**
Rebecca Stambler96954832019-09-15 20:25:54 -04004
Rebecca Stamblerd78b04b2020-12-28 13:26:14 -05005`gopls` exposes some (but not all) features on the command-line. This can be useful for debugging `gopls` itself.
Rebecca Stambler96954832019-09-15 20:25:54 -04006
Rebecca Stamblerd78b04b2020-12-28 13:26:14 -05007<!--TODO(rstambler): Generate this file.-->
Rebecca Stambler96954832019-09-15 20:25:54 -04008
Rebecca Stamblerd78b04b2020-12-28 13:26:14 -05009Learn about available commands and flags by running `gopls help`.
Rebecca Stambler96954832019-09-15 20:25:54 -040010
Rebecca Stamblerd78b04b2020-12-28 13:26:14 -050011Much of the functionality of `gopls` is available through a command line interface.
Rebecca Stambler96954832019-09-15 20:25:54 -040012
Rebecca Stamblerd78b04b2020-12-28 13:26:14 -050013There are two main reasons for this. The first is that we do not want users to rely on separate command line tools when they wish to do some task outside of an editor. The second is that the CLI assists in debugging. It is easier to reproduce behavior via single command.
14
15It is not a goal of `gopls` to be a high performance command line tool. Its command line is intended for single file/package user interaction speeds, not bulk processing.