Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

File References in Copied Chat Responses Are Not Formatted as Inline Code #236655

Open
pmontp19 opened this issue Dec 19, 2024 · 1 comment
Open
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug

Comments

@pmontp19
Copy link

When copying responses from the chat, the overall format (e.g., headings, code blocks, bullet points) is preserved. However, file references within the chat are not formatted correctly when copied. These file references, which are clickable in the chat, are copied with a line break before and after the file or symbol name and are not styled as inline code.

Expected Behavior: File references should be copied as inline code with proper markdown formatting (e.g., filename).

  • Copilot Chat Extension Version: 0.23.2
  • VS Code Version: 1.96.0
  • OS Version: OS X 15.1.1
  • Logs:

Steps to Reproduce:

  1. Generate a response that includes file references or code markup in the chat.
  2. Right-click the response and select Copy.
@rebornix rebornix assigned roblourens and unassigned digitarald Dec 19, 2024
@mjbvz mjbvz self-assigned this Dec 19, 2024
@mjbvz mjbvz transferred this issue from microsoft/vscode-copilot-release Dec 19, 2024
@mjbvz mjbvz assigned mjbvz and unassigned mjbvz and roblourens Dec 19, 2024
@mjbvz mjbvz added the bug Issue identified by VS Code Team member as probable bug label Dec 19, 2024
Copy link

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.96.2. Please try upgrading to the latest version and checking whether this issue remains.

Happy Coding!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issue identified by VS Code Team member as probable bug
Projects
None yet
Development

No branches or pull requests

5 participants