about summary refs log tree commit diff
path: root/tests/incremental/thinlto
diff options
context:
space:
mode:
authorElias Holzmann <9659253+EliasHolzmann@users.noreply.github.com>2023-10-08 03:31:23 +0200
committerElias Holzmann <9659253+EliasHolzmann@users.noreply.github.com>2023-10-08 04:56:48 +0200
commit3dfc1bfc67c9779ec3c936c1987349ac77cd8af4 (patch)
tree3ef074c3ba04c3da0f814992142833ff12b66ebf /tests/incremental/thinlto
parentb1f89a84ab350091e6c20cfe30c2fab8d76b80e4 (diff)
downloadrust-3dfc1bfc67c9779ec3c936c1987349ac77cd8af4.tar.gz
rust-3dfc1bfc67c9779ec3c936c1987349ac77cd8af4.zip
Use vscode.env.openExternal instead of the vscode.open command for docs
According to the VS Code documentation, the vscode.open command opens the URL
_in the editor_ (https://code.visualstudio.com/api/references/commands).
However, in reality, it seems to do so only for file:// URLs, falling back to
other applications for other URL schemes (at least for HTTP/HTTPS).

Until now, the URL to the documentation was always HTTP based, so using the
vscode.open command was perfectly fine. However, displaying local documentation
will be supported from now on (see next commit). Local documentation is not
HTTP-based, but instead addressed via a file:// URL. The file URL would
therefore be opened in VS Code instead of in the browser — this is definitely
not what the user wants.

Therefore, the vscode.env.openExternal function is used instead, this function
never opens the URL in VS Code.
Diffstat (limited to 'tests/incremental/thinlto')
0 files changed, 0 insertions, 0 deletions