Let users set the completion file path, in current format it needs us to manually move the file to specific location.

I have installed bazel with linuxbrew and it sits somewhere in /home/linuxbrew/.linuxbrew.

Instead I can keep a copy of bazel-completion.bash somewhere like ~/.config/bash and just set bash_completion_path in vimrc

The vim-bazel README and/or help files should mention the related plugin https://github.com/bazelbuild/vim-ft-bzl that defines the filetype (ftdetect, syntax, and other basic filetype settings) so users who just find this plugin aren't left wondering where the filetype files are.

It would be nice if the bazel plugin could infer "the target for the current file" automatically so you could just invoke :Bazel build or :Bazel test as a shortcut for "build this file's build target" and "run the test defined in this file".

Hi,

I'm using vim 8.2, vim-go (latest), errcheck (latest), and vim-bazel (latest) on macOS Catalina. I'm using go_proto_library() to compile a protobuf, but vim-go flags my import as being not found despite Bazel successfully compiling it.

It's not that big of a deal because it's a warning I can ignore, but I was wondering if there's something quick and easy I can do to make it go away.

Thanks!

If a :Bazel build command fails, users should be able to browse the individual error messages from within vim and jump to the referenced file locations via something like the quickfix list.

Note that actually processing bazel output and extracting file location information from any given message will be surprisingly complex. We may want a helper tool to that we can pipe bazel's output to parse log output, handling the idiosyncracies of different kinds of tool output and converting them to a single machine-readable format.

The target completion did not work without explicitly setting the path via

bazel#SetBashCompletionPath('/etc/bash_completion.d/bazel-complete.bash')

I would suggest to change the default path according to the docs https://docs.bazel.build/versions/main/completion.html:

 if !exists('s:bash_completion_path')
-  let s:bash_completion_path = '/etc/bash_completion.d/bazel'
+  let s:bash_completion_path = '/etc/bash_completion.d/bazel-complete.bash'
 endif

See:

If you invoke a slow bazel build that takes seconds or minutes, the build will currently steal focus and execute in the foreground, preventing you from doing anything else in your vim session until it finishes. It would be nice to have the build continue in the background and leave vim fully usable while it's running (possibly in some kind of interactive shell mode where you can see the bazel cli output as it's printed).

Vim 8's new job support looks like it will suit our needs. In Neovim, there's probably a native API to do what we want.

Hi, all. Thank you for this plugin.
Today came across issue that Bazel binary cant be found by this plugin.
That was because i was using plain alias bazel='bazelisk' in my ~/.zshrc.
The fix of this was just a simple sudo ln -s /usr/local/bin/bazelisk /usr/local/bin/bazel. I think this could augment the readme of this plugin pretty well.