From 5a2238daf50e6375025e596ec186df4f4429aaf8 Mon Sep 17 00:00:00 2001 From: lberki Date: Fri, 18 May 2018 03:15:32 -0700 Subject: Remove "bazel run --nodirect_run". RELNOTES[INC]: Bazel now always runs binaries in with "bazel run" in interactive mode. The "--nodirect_run" command line option is now a no-op. PiperOrigin-RevId: 197121535 --- site/docs/user-manual.html | 13 ++++--------- 1 file changed, 4 insertions(+), 9 deletions(-) (limited to 'site') diff --git a/site/docs/user-manual.html b/site/docs/user-manual.html index 3b28c49634..6d93e7dca1 100644 --- a/site/docs/user-manual.html +++ b/site/docs/user-manual.html @@ -3000,11 +3000,6 @@ Examples: --arg2 -

- Bazel closes stdin, so you can't use bazel run - if you want to start an interactive program or pipe data to it. -

-

Note the use of the --. This is needed so that Bazel does not interpret --arg1 and --arg2 as @@ -3027,10 +3022,10 @@ Examples:

bazel run can also execute test binaries, which has the effect of -running the test, but without the setup documented on the page -Writing Tests, so that the test runs -in an environment closer to the current shell environment. Note that none of the ---test_* arguments have an effect when running a test in this manner. + running the test in a close approximation of the environment described at + Writing Tests. Note that none of the + --test_*code> arguments have an effect when running a test in this manner except + --test_arg .

Querying the dependency graph with Bazel

-- cgit v1.2.3