Change:
Type: <bBug</bfile: line xxx link cannot be recognized in pwsh terminal. In pwsh terminal, if the program return error (eg. ObjectStore.Save(f"chart" in line 35) line 35, when you hold ctrl and try to click " line 35" to navigate to the error code line, it always fails. But it's OK in cmd terminal. Please fix this issue for pwsh is more powerful and easy to use than CMD. Thanks. VS Code version: Code 1.81.1 (, 2023-08-09T22:22:42.175Z) OS version: WindowsNT x64 10.0. Modes: <details<summarySystem Info</summary </details<details<summaryExtensions (22)</summaryExtensionVersion ------ format-json1.0.3 gitlens14.2.1 git-project-manager1.8.2 copilot1.104.347 copilot-chat0.7. copilot-labs0.14.884 rainbow-csv3.7.0 vscode-docker1.26.0 csharp2.0.376 vscode-dotnet-runtime1.7.0 python2023.14.0 vscode-pylance2023.8.30 jupyter2023.7. jupyter-keymap1.1.2 jupyter-renderers1.0.17 vscode-jupyter-cell-tags0.1.8 vscode-jupyter-slideshow0.1.5 remote-containers0.304.0 remote-wsl0.81.0 autodocstring0.6.1 intellicode-api-usage-examples0.2.7 vscodeintellicode1.2.30 (2 theme extensions excluded) </details<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --
what command did you run to get that output?
lean backtest xxxx. lean is quantconnect product and it run python code on docker and return some messages on terminal. pip install lean to install this tool :19Daniel Imms what command did you run to get that output? —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID:
Looking into this more, this would actually be a feature request. We do support the format for validated links, but we are not smart about including the line/col number when searching for a file like with a word link. The current behavior when clicking is: ! Ideal: ! If anyone wants to give this a shot, it would involve hooking up in

Discussion:
uri?: URI; /** <ins> * An optional full line to be used for context when resolving. */ contextLine?: string; /** </ins> * The location or selection range of the link. */ selection?: ITextEditorSelection;

import { QueryBuilder } from 'vs/workbench/services/search/common/queryBuilder'; import { ISearchService } from 'vs/workbench/services/search/common/search'; import { IConfigurationService } from 'vs/platform/configuration/common/configuration'; <del> import { getLinkSuffix } from 'vs/workbench/contrib/terminalContrib/links/browser/terminalLinkParsing'; </del> <ins> import { detectLinks, getLinkSuffix } from 'vs/workbench/contrib/terminalContrib/links/browser/terminalLinkParsing'; </ins> import { ITerminalLogService } from 'vs/platform/terminal/common/terminal'; export class TerminalLocalFileLinkOpener implements ITerminalLinkOpener {

async open(link: ITerminalSimpleLink): Promise<void> { const osPath = osPathModule(this._getOS()); const pathSeparator = osPath.sep; // Remove file:/// and any leading ./ or ../ since quick access doesn't understand that format let text = link.text.replace(/^file:///?/, ''); text = osPath.normalize(text).replace(/^(.+[/])+/, ''); <ins> // Try extract any trailing line and column numbers by matching the text against parsed // links. This will give a search link `foo` on a line like `"foo", line 10` to open the // quick pick with `foo:10` as the contents. if (link.contextLine) { const parsedLinks = detectLinks(link.contextLine, this._getOS()); const matchingParsedLink = parsedLinks.find(parsedLink => parsedLink.suffix && link.text === parsedLink.path.text); if (matchingParsedLink) { if (matchingParsedLink.suffix?.row !== undefined) { text += `:${matchingParsedLink.suffix.row}`; if (matchingParsedLink.suffix?.col !== undefined) { text += `:${matchingParsedLink.suffix.col}`; } } } } </ins> // Remove `:<one or more non number characters>` from the end of the link. // Examples: // - Ruby stack traces: <link>:in ...

links.push({ text: word.text, bufferRange, <del> type: TerminalBuiltinLinkType.Search </del> <ins> type: TerminalBuiltinLinkType.Search, contextLine: text </ins> }); }