John Firebaugh

Okay, I got further with a `./` prefix but I'm still stuck. Here's a minimal repro: https://github.com/jfirebaugh/rules_xcode_reduction/tree/454cf9eef2e7c5464147f43b6e75ade1bcd3911c. When I run `./wrapper.sh run :xcodeproj && open open app.xcodeproj/` and then build...

Figured out that that's caused by the `echo` in the wrapper.

Now the issue I have is that when I open the Xcode project, something generates a directory named `--compilation_mode=dbg/` with what looks like the contents of a Bazel output directory...

I eventually got the minimized test case [working](https://github.com/jfirebaugh/rules_xcode_reduction/tree/5783b79c3d26fb48afc175ec0b6669713a1dd151) with: ``` case "$1" in build | run | test) args=("$@") bazel "${args[0]}" --compilation_mode=dbg "${args[@]:1}" ;; *) bazel "$@" ;; esac ```...

It still happens if I change the wrapper to `build | run | test | info)`.

This seems like more of a special case of the draw area mode than an operation.

I also find the change from two-finger trackpad zoom to two-finger trackpad pan quite jarring. It's contrary to how the vast majority of maps on the web work, including the...

Plus I've hit #5552 about a half-dozen times in 10 minutes of editing.

I think this is a consequence of Leaflet's SVG implementation and probably not simple to fix. /cc @mourner

> While we're on the subject, it would help if it were possible to reference `${workspaceFolder}` in the path. This is https://github.com/bazelbuild/vscode-bazel/issues/132.