// Please enter a detailed description of the issue // Description of the issue:

Feature request: it would be great if Marked could (be configured to) open a new markdown document in a new tab of an existing window, rather than always in a new window. If there's more than one window open, then the top-most one.

Whenever I open a new markdown document, the first thing I do, almost always, is to move the tab to a currently-visible window. This helps keep down the number of Marked windows, and keep markdown files in related clusters (easier to tab between them).

In UI terms, I'd expect to see this in the 'General' pane, near 'Keep new windows on top'. The way I use Marked, this seems like an obvious functionality, so if this already exists, and I've just not found the setting, sorry.

(and thanks for the rays of sunshine in the release notes...)

// Please enter a list of steps required to reproduce the issue // Steps to reproduce:

n/a

// If applicable please attach a sample document that causes the issue for you.

// Configuration (do not edit) Marked 2 1010 (Direct)

macOS Version: 10.15.7

additionalMathJaxConfig:
allowPageBreakInCode: YES
bookTxtIsLeanpub: NO
summaryMdIsGitBook: NO
codeIsPoetry: NO
codeCanWrap: YES
collapsibleHeadlines: YES
convertGithubCheckboxes: YES
convertYAMLToMMD: NO
defaultMathJaxConfig: TeX-AMS-MML_HTMLorMML
defaultPreviewStyle: 3
defaultProcessor: MultiMarkdown
enableMiniMap: YES
excludeBlockQuotesFromCounts: NO
excludeFootnotesFromCounts: NO
excludeVerbatimFromCounts: NO
excludeCaptionsFromCounts: NO
folderPreviewExtensionsArray: md, markdown, txt, mdown, html, opml
githubNewlines: NO
h1IsPageBreak: YES
h2IsPageBreak: NO
hrIsPageBreak: NO
includeMathJax: YES
includeKatex: NO
limitTextWidth: NO
minimalJavaScript: NO
outlineModeExtensions:
permissionGranted: NO
printHeaderBottomLeft:
printHeaderBottomRight:
printHeaderFirstPage: NO
printFooterFirstPage: NO
printHeaderTopLeft:
printHeaderTopRight:
processHTMLFiles: YES
removeMetadataForPreview: NO
removeYAMLHeaders: NO
scrollToEdit: YES
shouldDetectCritic: NO
shouldHighlightMarkupErrors: YES
shouldLoadCritic: NO
syntaxHighlight: NO
syntaxHighlightOnlyLang: NO
useCustomMarkdownProcessor: NO
customMarkdownProcessor:
useCustomPreprocessor: NO
customPreprocessor:
useFirstH1AsPrintTitle: YES