Please do not convert to your new markdown editor, keep the "Open in Preview"

Ideas Feedback
1

In 2.4, you change to a new markdown editor that combines Preview and Markdown view into the same pane and removes the dual pane preview in VS Code.

Please make this an option because the UX is a total regression in editing and previewing markdown. If Cursor forces this UX, I’ll have to move back to VS Code

3

Hey, thanks for the feedback.

Could you describe in more detail which scenarios the old dual-pane preview was more convenient for? For example, was this about editing docs, notes, or other specific use cases?

It’d also help if you could show exactly what changed: a screenshot of the current behavior, and how it worked before in VS Code.

I’ll pass this along to the team, but to make a stronger case we need more context.

4

i rely on yaml headers for indexing; this makes it gross to work with. also the latex looks terrible.

image
image1842×702 35.9 KB