quarto-dev
diff --git a/‎src/resources/editor/tools/vs-code.mjs‎
Lines changed: 14 additions & 13 deletions b/‎src/resources/editor/tools/vs-code.mjs‎
Lines changed: 14 additions & 13 deletions
@@ -8531,12 +8531,13 @@ var require_yaml_intelligence_resources = __commonJS({
                                 {
                                   enum: [
                                     "always",
+                                    "whenSidebarOpen",
                                     "never"
                                   ]
                                 }
                               ],
                               default: "always",
-                              description: "Controls whether the in-document highlights are shown by default (`always` or `never`)"
+                              description: "Controls whether the in-document highlights are shown by default (`always`, `whenSidebarOpen` or `never`)"
                             },
                             theme: {
                               enum: [
@@ -13489,7 +13490,7 @@ var require_yaml_intelligence_resources = __commonJS({
               ]
             }
           },
-          description: 'Include contents at the beginning of the document body\n(e.g. after the `<body>` tag in HTML, or the `\\begin{document}` command \nin LaTeX).\n\nA string value or an object with key "file" indicates a filename whose contents are to be included\n\nAn object with key "text" indicates textual content to be included\n'
+          description: 'Include contents at the beginning of the document body\n(e.g. after the `<body>` tag in HTML, or the `\\begin{document}` command\nin LaTeX).\n\nA string value or an object with key "file" indicates a filename whose contents are to be included\n\nAn object with key "text" indicates textual content to be included\n'
         },
         {
           name: "include-after-body",
@@ -13508,7 +13509,7 @@ var require_yaml_intelligence_resources = __commonJS({
               ]
             }
           },
-          description: 'Include contents at the end of the document body (before\nthe `</body>` tag in HTML, or the `\\end{document}` command in LaTeX).\n\nA string value or an object with key "file" indicates a filename whose contents are to be included\n\nAn object with key "text" indicates textual content to be included\n'
+          description: 'Include content at the end of the document body immediately after the markdown content. While it will be included before the closing `</body>` tag in HTML and the `\\end{document}` command in LaTeX, this option refers to the end of the markdown content.\n\nA string value or an object with key "file" indicates a filename whose contents are to be included\n\nAn object with key "text" indicates textual content to be included\n'
         },
         {
           name: "include-in-header",
@@ -13527,7 +13528,7 @@ var require_yaml_intelligence_resources = __commonJS({
               ]
             }
           },
-          description: 'Include contents at the end of the header. This can\nbe used, for example, to include special CSS or JavaScript in HTML \ndocuments.\n\nA string value or an object with key "file" indicates a filename whose contents are to be included\n\nAn object with key "text" indicates textual content to be included\n'
+          description: 'Include contents at the end of the header. This can\nbe used, for example, to include special CSS or JavaScript in HTML\ndocuments.\n\nA string value or an object with key "file" indicates a filename whose contents are to be included\n\nAn object with key "text" indicates textual content to be included\n'
         },
         {
           name: "resources",
@@ -13553,7 +13554,7 @@ var require_yaml_intelligence_resources = __commonJS({
           },
           description: {
             short: "Text to be in a running header.",
-            long: "Text to be in a running header.\n\nProvide a single option or up to four options for different placements \n(odd page inner, odd page outer, even page innner, even page outer).\n"
+            long: "Text to be in a running header.\n\nProvide a single option or up to four options for different placements\n(odd page inner, odd page outer, even page innner, even page outer).\n"
           }
         },
         {
@@ -13568,7 +13569,7 @@ var require_yaml_intelligence_resources = __commonJS({
           },
           description: {
             short: "Text to be in a running footer.",
-            long: "Text to be in a running footer.\n\nProvide a single option or up to four options for different placements \n(odd page inner, odd page outer, even page innner, even page outer).\n\nSee [ConTeXt Headers and Footers](https://wiki.contextgarden.net/Headers_and_Footers) for more information.\n"
+            long: "Text to be in a running footer.\n\nProvide a single option or up to four options for different placements\n(odd page inner, odd page outer, even page innner, even page outer).\n\nSee [ConTeXt Headers and Footers](https://wiki.contextgarden.net/Headers_and_Footers) for more information.\n"
           }
         },
         {
@@ -13608,7 +13609,7 @@ var require_yaml_intelligence_resources = __commonJS({
           hidden: true,
           description: {
             short: "Include file with YAML metadata",
-            long: "Read metadata from the supplied YAML (or JSON) file. This\noption can be used with every input format, but string scalars\nin the YAML file will always be parsed as Markdown. Generally,\nthe input will be handled the same as in YAML metadata blocks.\nMetadata values specified inside the document, or by using `-M`, \noverwrite values specified with this option.\n"
+            long: "Read metadata from the supplied YAML (or JSON) file. This\noption can be used with every input format, but string scalars\nin the YAML file will always be parsed as Markdown. Generally,\nthe input will be handled the same as in YAML metadata blocks.\nMetadata values specified inside the document, or by using `-M`,\noverwrite values specified with this option.\n"
           }
         },
         {
@@ -13618,7 +13619,7 @@ var require_yaml_intelligence_resources = __commonJS({
           },
           description: {
             short: "Include files with YAML metadata",
-            long: "Read metadata from the supplied YAML (or JSON) files. This\noption can be used with every input format, but string scalars\nin the YAML file will always be parsed as Markdown. Generally,\nthe input will be handled the same as in YAML metadata blocks.\nValues in files specified later in the list will be preferred\nover those specified earlier. Metadata values specified inside \nthe document, or by using `-M`, overwrite values specified with\nthis option.\n"
+            long: "Read metadata from the supplied YAML (or JSON) files. This\noption can be used with every input format, but string scalars\nin the YAML file will always be parsed as Markdown. Generally,\nthe input will be handled the same as in YAML metadata blocks.\nValues in files specified later in the list will be preferred\nover those specified earlier. Metadata values specified inside\nthe document, or by using `-M`, overwrite values specified with\nthis option.\n"
           }
         }
       ],
@@ -18232,7 +18233,7 @@ var require_yaml_intelligence_resources = __commonJS({
         "The giscus theme to use when displaying comments.",
         "The language that should be used when displaying the commenting\ninterface.",
         "Controls whether the sidebar opens automatically on startup.",
-        "Controls whether the in-document highlights are shown by default\n(<code>always</code> or <code>never</code>)",
+        "Controls whether the in-document highlights are shown by default\n(<code>always</code>, <code>whenSidebarOpen</code> or\n<code>never</code>)",
         "Controls the overall look of the sidebar (<code>classic</code> or\n<code>clean</code>)",
         "Controls whether the experimental New Note button should be shown in\nthe notes tab in the sidebar.",
         "Specify a URL to direct a user to, in a new tab. when they click on\nthe annotation author link in the header of an annotation.",
@@ -19843,7 +19844,7 @@ var require_yaml_intelligence_resources = __commonJS({
         "Content to include at the beginning of the document body (e.g.&nbsp;after\nthe <code>&lt;body&gt;</code> tag in HTML, or the\n<code>\\begin{document}</code> command in LaTeX).",
         "Content to include at the end of the document body (before the\n<code>&lt;/body&gt;</code> tag in HTML, or the\n<code>\\end{document}</code> command in LaTeX).",
         "Include contents at the beginning of the document body (e.g.&nbsp;after\nthe <code>&lt;body&gt;</code> tag in HTML, or the\n<code>\\begin{document}</code> command in LaTeX).\nA string value or an object with key \u201Cfile\u201D indicates a filename\nwhose contents are to be included\nAn object with key \u201Ctext\u201D indicates textual content to be\nincluded",
-        "Include contents at the end of the document body (before the\n<code>&lt;/body&gt;</code> tag in HTML, or the\n<code>\\end{document}</code> command in LaTeX).\nA string value or an object with key \u201Cfile\u201D indicates a filename\nwhose contents are to be included\nAn object with key \u201Ctext\u201D indicates textual content to be\nincluded",
+        "Include content at the end of the document body, immediately after\nthe markdown content. While the content will be included before the\nclosing <code>&lt;/body&gt;</code> tag in HTML and the\n<code>\\end{document}</code> command in LaTeX, this option specifically\nrefers to the end of the content.\nA string value or an object with key \u201Cfile\u201D indicates a filename\nwhose contents are to be included\nAn object with key \u201Ctext\u201D indicates textual content to be\nincluded",
         "Include contents at the end of the header. This can be used, for\nexample, to include special CSS or JavaScript in HTML documents.\nA string value or an object with key \u201Cfile\u201D indicates a filename\nwhose contents are to be included\nAn object with key \u201Ctext\u201D indicates textual content to be\nincluded",
         "Path (or glob) to files to publish with this document.",
         {
@@ -21233,12 +21234,12 @@ var require_yaml_intelligence_resources = __commonJS({
         mermaid: "%%"
       },
       "handlers/mermaid/schema.yml": {
-        _internalId: 151733,
+        _internalId: 151732,
         type: "object",
         description: "be an object",
         properties: {
           "mermaid-format": {
-            _internalId: 151725,
+            _internalId: 151724,
             type: "enum",
             enum: [
               "png",
@@ -21254,7 +21255,7 @@ var require_yaml_intelligence_resources = __commonJS({
             exhaustiveCompletions: true
           },
           theme: {
-            _internalId: 151732,
+            _internalId: 151731,
             type: "anyOf",
             anyOf: [
               {
Original file line number	Diff line number	Diff line change
`@@ -8531,12 +8531,13 @@ var require_yaml_intelligence_resources = __commonJS({`
`8531`	`8531`	`{`
`8532`	`8532`	`enum: [`
`8533`	`8533`	`"always",`
	`8534`	`+ "whenSidebarOpen",`
`8534`	`8535`	`"never"`
`8535`	`8536`	`]`
`8536`	`8537`	`}`
`8537`	`8538`	`],`
`8538`	`8539`	`default: "always",`
`8539`		- description: "Controls whether the in-document highlights are shown by default (`always` or `never`)"
	`8540`	+ description: "Controls whether the in-document highlights are shown by default (`always`, `whenSidebarOpen` or `never`)"
`8540`	`8541`	`},`
`8541`	`8542`	`theme: {`
`8542`	`8543`	`enum: [`
`@@ -13489,7 +13490,7 @@ var require_yaml_intelligence_resources = __commonJS({`
`13489`	`13490`	`]`
`13490`	`13491`	`}`
`13491`	`13492`	`},`
`13492`		- description: 'Include contents at the beginning of the document body\n(e.g. after the `<body>` tag in HTML, or the `\\begin{document}` command \nin LaTeX).\n\nA string value or an object with key "file" indicates a filename whose contents are to be included\n\nAn object with key "text" indicates textual content to be included\n'
	`13493`	+ description: 'Include contents at the beginning of the document body\n(e.g. after the `<body>` tag in HTML, or the `\\begin{document}` command\nin LaTeX).\n\nA string value or an object with key "file" indicates a filename whose contents are to be included\n\nAn object with key "text" indicates textual content to be included\n'
`13493`	`13494`	`},`
`13494`	`13495`	`{`
`13495`	`13496`	`name: "include-after-body",`
`@@ -13508,7 +13509,7 @@ var require_yaml_intelligence_resources = __commonJS({`
`13508`	`13509`	`]`
`13509`	`13510`	`}`
`13510`	`13511`	`},`
`13511`		- description: 'Include contents at the end of the document body (before\nthe `</body>` tag in HTML, or the `\\end{document}` command in LaTeX).\n\nA string value or an object with key "file" indicates a filename whose contents are to be included\n\nAn object with key "text" indicates textual content to be included\n'
	`13512`	+ description: 'Include content at the end of the document body immediately after the markdown content. While it will be included before the closing `</body>` tag in HTML and the `\\end{document}` command in LaTeX, this option refers to the end of the markdown content.\n\nA string value or an object with key "file" indicates a filename whose contents are to be included\n\nAn object with key "text" indicates textual content to be included\n'
`13512`	`13513`	`},`
`13513`	`13514`	`{`
`13514`	`13515`	`name: "include-in-header",`
`@@ -13527,7 +13528,7 @@ var require_yaml_intelligence_resources = __commonJS({`
`13527`	`13528`	`]`
`13528`	`13529`	`}`
`13529`	`13530`	`},`
`13530`		`- description: 'Include contents at the end of the header. This can\nbe used, for example, to include special CSS or JavaScript in HTML \ndocuments.\n\nA string value or an object with key "file" indicates a filename whose contents are to be included\n\nAn object with key "text" indicates textual content to be included\n'`
	`13531`	`+ description: 'Include contents at the end of the header. This can\nbe used, for example, to include special CSS or JavaScript in HTML\ndocuments.\n\nA string value or an object with key "file" indicates a filename whose contents are to be included\n\nAn object with key "text" indicates textual content to be included\n'`
`13531`	`13532`	`},`
`13532`	`13533`	`{`
`13533`	`13534`	`name: "resources",`
`@@ -13553,7 +13554,7 @@ var require_yaml_intelligence_resources = __commonJS({`
`13553`	`13554`	`},`
`13554`	`13555`	`description: {`
`13555`	`13556`	`short: "Text to be in a running header.",`
`13556`		`- long: "Text to be in a running header.\n\nProvide a single option or up to four options for different placements \n(odd page inner, odd page outer, even page innner, even page outer).\n"`
	`13557`	`+ long: "Text to be in a running header.\n\nProvide a single option or up to four options for different placements\n(odd page inner, odd page outer, even page innner, even page outer).\n"`
`13557`	`13558`	`}`
`13558`	`13559`	`},`
`13559`	`13560`	`{`
`@@ -13568,7 +13569,7 @@ var require_yaml_intelligence_resources = __commonJS({`
`13568`	`13569`	`},`
`13569`	`13570`	`description: {`
`13570`	`13571`	`short: "Text to be in a running footer.",`
`13571`		`- long: "Text to be in a running footer.\n\nProvide a single option or up to four options for different placements \n(odd page inner, odd page outer, even page innner, even page outer).\n\nSee [ConTeXt Headers and Footers](https://wiki.contextgarden.net/Headers_and_Footers) for more information.\n"`
	`13572`	`+ long: "Text to be in a running footer.\n\nProvide a single option or up to four options for different placements\n(odd page inner, odd page outer, even page innner, even page outer).\n\nSee [ConTeXt Headers and Footers](https://wiki.contextgarden.net/Headers_and_Footers) for more information.\n"`
`13572`	`13573`	`}`
`13573`	`13574`	`},`
`13574`	`13575`	`{`
`@@ -13608,7 +13609,7 @@ var require_yaml_intelligence_resources = __commonJS({`
`13608`	`13609`	`hidden: true,`
`13609`	`13610`	`description: {`
`13610`	`13611`	`short: "Include file with YAML metadata",`
`13611`		- long: "Read metadata from the supplied YAML (or JSON) file. This\noption can be used with every input format, but string scalars\nin the YAML file will always be parsed as Markdown. Generally,\nthe input will be handled the same as in YAML metadata blocks.\nMetadata values specified inside the document, or by using `-M`, \noverwrite values specified with this option.\n"
	`13612`	+ long: "Read metadata from the supplied YAML (or JSON) file. This\noption can be used with every input format, but string scalars\nin the YAML file will always be parsed as Markdown. Generally,\nthe input will be handled the same as in YAML metadata blocks.\nMetadata values specified inside the document, or by using `-M`,\noverwrite values specified with this option.\n"
`13612`	`13613`	`}`
`13613`	`13614`	`},`
`13614`	`13615`	`{`
`@@ -13618,7 +13619,7 @@ var require_yaml_intelligence_resources = __commonJS({`
`13618`	`13619`	`},`
`13619`	`13620`	`description: {`
`13620`	`13621`	`short: "Include files with YAML metadata",`
`13621`		- long: "Read metadata from the supplied YAML (or JSON) files. This\noption can be used with every input format, but string scalars\nin the YAML file will always be parsed as Markdown. Generally,\nthe input will be handled the same as in YAML metadata blocks.\nValues in files specified later in the list will be preferred\nover those specified earlier. Metadata values specified inside \nthe document, or by using `-M`, overwrite values specified with\nthis option.\n"
	`13622`	+ long: "Read metadata from the supplied YAML (or JSON) files. This\noption can be used with every input format, but string scalars\nin the YAML file will always be parsed as Markdown. Generally,\nthe input will be handled the same as in YAML metadata blocks.\nValues in files specified later in the list will be preferred\nover those specified earlier. Metadata values specified inside\nthe document, or by using `-M`, overwrite values specified with\nthis option.\n"
`13622`	`13623`	`}`
`13623`	`13624`	`}`
`13624`	`13625`	`],`
`@@ -18232,7 +18233,7 @@ var require_yaml_intelligence_resources = __commonJS({`
`18232`	`18233`	`"The giscus theme to use when displaying comments.",`
`18233`	`18234`	`"The language that should be used when displaying the commenting\ninterface.",`
`18234`	`18235`	`"Controls whether the sidebar opens automatically on startup.",`
`18235`		`- "Controls whether the in-document highlights are shown by default\n(<code>always</code> or <code>never</code>)",`
	`18236`	`+ "Controls whether the in-document highlights are shown by default\n(<code>always</code>, <code>whenSidebarOpen</code> or\n<code>never</code>)",`
`18236`	`18237`	`"Controls the overall look of the sidebar (<code>classic</code> or\n<code>clean</code>)",`
`18237`	`18238`	`"Controls whether the experimental New Note button should be shown in\nthe notes tab in the sidebar.",`
`18238`	`18239`	`"Specify a URL to direct a user to, in a new tab. when they click on\nthe annotation author link in the header of an annotation.",`
`@@ -19843,7 +19844,7 @@ var require_yaml_intelligence_resources = __commonJS({`
`19843`	`19844`	`"Content to include at the beginning of the document body (e.g. after\nthe <code><body></code> tag in HTML, or the\n<code>\\begin{document}</code> command in LaTeX).",`
`19844`	`19845`	`"Content to include at the end of the document body (before the\n<code></body></code> tag in HTML, or the\n<code>\\end{document}</code> command in LaTeX).",`
`19845`	`19846`	`"Include contents at the beginning of the document body (e.g. after\nthe <code><body></code> tag in HTML, or the\n<code>\\begin{document}</code> command in LaTeX).\nA string value or an object with key \u201Cfile\u201D indicates a filename\nwhose contents are to be included\nAn object with key \u201Ctext\u201D indicates textual content to be\nincluded",`
`19846`		`- "Include contents at the end of the document body (before the\n<code></body></code> tag in HTML, or the\n<code>\\end{document}</code> command in LaTeX).\nA string value or an object with key \u201Cfile\u201D indicates a filename\nwhose contents are to be included\nAn object with key \u201Ctext\u201D indicates textual content to be\nincluded",`
	`19847`	+ "Include content at the end of the document body, immediately after\nthe markdown content. While the content will be included before the\nclosing <code></body></code> tag in HTML and the\n<code>\\end{document}</code> command in LaTeX, this option specifically\nrefers to the end of the content.\nA string value or an object with key \u201Cfile\u201D indicates a filename\nwhose contents are to be included\nAn object with key \u201Ctext\u201D indicates textual content to be\nincluded",
`19847`	`19848`	`"Include contents at the end of the header. This can be used, for\nexample, to include special CSS or JavaScript in HTML documents.\nA string value or an object with key \u201Cfile\u201D indicates a filename\nwhose contents are to be included\nAn object with key \u201Ctext\u201D indicates textual content to be\nincluded",`
`19848`	`19849`	`"Path (or glob) to files to publish with this document.",`
`19849`	`19850`	`{`
`@@ -21233,12 +21234,12 @@ var require_yaml_intelligence_resources = __commonJS({`
`21233`	`21234`	`mermaid: "%%"`
`21234`	`21235`	`},`
`21235`	`21236`	`"handlers/mermaid/schema.yml": {`
`21236`		`- _internalId: 151733,`
	`21237`	`+ _internalId: 151732,`
`21237`	`21238`	`type: "object",`
`21238`	`21239`	`description: "be an object",`
`21239`	`21240`	`properties: {`
`21240`	`21241`	`"mermaid-format": {`
`21241`		`- _internalId: 151725,`
	`21242`	`+ _internalId: 151724,`
`21242`	`21243`	`type: "enum",`
`21243`	`21244`	`enum: [`
`21244`	`21245`	`"png",`
`@@ -21254,7 +21255,7 @@ var require_yaml_intelligence_resources = __commonJS({`
`21254`	`21255`	`exhaustiveCompletions: true`
`21255`	`21256`	`},`
`21256`	`21257`	`theme: {`
`21257`		`- _internalId: 151732,`
	`21258`	`+ _internalId: 151731,`
`21258`	`21259`	`type: "anyOf",`
`21259`	`21260`	`anyOf: [`
`21260`	`21261`	`{`