Verified Solution

[microsoft/vscode] Feature Request: Add vscode setting to open markdown file links in Integrated Browser instead of default external browser

Sponsored Content
### ROOT CAUSE The issue arises because the default behavior for opening markdown links in VS Code is to use the external browser. This behavior is hardcoded in the markdown extension's click handler, which uses `vscode.env.openExternal(uri)` to open links. There is no configuration option to change this behavior. ### CODE FIX To implement the requested feature, modify the markdown extension's click handler to check a new setting before opening links: 1. **Add a setting in `package.json`:** ```json { "contributes": { "configuration": { "properties": { "markdown.openExternalLinks": { "type": "boolean", "default": true, "description": "Open markdown links in external browser (default) or integrated browser (when false)." } } } } } ``` 2. **Update the click handler code (in markdown extension):** ```typescript // In the markdown extension's click handler (e.g., markdown.action.openLink) if (!settings.markdown.openExternalLinks) { // Use integrated browser (new tab in VS Code) vscode.commands.executeCommand('vscode.open', uri); } else { // Use external browser vscode.env.openExternal(uri); } ``` This change introduces a configurable setting (`markdown.openExternalLinks`) to toggle between external and integrated browser behavior for markdown links.
Deploy on DigitalOcean ($200 Credit)

Related Fixes

[pytorch/pytorch] MPS: scaled_dot_product_attention returns wrong output shape when value dim != query/key dim
[StackOverflow/rust] trouble getting sqlx #[derive(sqlx::Type)] to work with a rust enum using MySQL/MariaDB
[gitlab-org/gitlab] [FF] Rollout read_project_push_rules, and write_project_push_rules feature flags on self-managed