-
Notifications
You must be signed in to change notification settings - Fork 30.4k
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
Preview Should Open in Same Tab #135216
Comments
There's a |
@mjbvz Yes, this opens the preview in a new tab. Please re-open my request. |
For that, use |
No, that also does not split the current tab into editor | preview. |
@mjbvz @cawoodm wouldn't this be a perfect fit for the "Split In Group" set of commands that was just released in 1.61? When it was released I thought surely markdown preview would be supported as part of that, but it seems like that wasn't added. |
For context, I use the following setting to automatically open Markdown Previews to the side when I open a Markdown file:
However, the annoying thing about this is that when you close out one of the tabs, you have to manually navigate over to the preview (or the editor) and close it out. I would like to treat the markdown raw text and the preview as a single "entity", and close them/open them at the same time. That seems to be essentially what @cawoodm is asking for here, and I don't believe that this is possible. I'm in agreement that this issue should be reopened, as it's not currently possible in VSCode. |
This should be a no-brainer - when I am editing a document I want to preview it on the right in the same tab and not in a separate tab or tab group. The default behaviours (open in new tab or open in new tab in new group) both mean that when I navigate away I have to manually manage getting back to 2 tab groups.
Back story - this was originally requested in #58525 and incorrectly closed and marked as a duplicate of #37883 which is a different issue/request.
The wish is that HTML/Markdown previews can open in the same TAB:
![image](https://user-images.githubusercontent.com/498834/137596955-956fca53-9e72-400e-abd7-62b643359841.png)
The text was updated successfully, but these errors were encountered: