| /third_party/rust/rust/src/doc/man/ |
| D | rustdoc.1 | 63 files to include inline between <body> and the content of a rendered Markdown
66 \fB\-\-markdown\-before\-content\fR \fIFILES\fR
68 Markdown file or generated documentation
72 Markdown file or generated documentation
74 \fB\-\-markdown\-after\-content\fR \fIFILES\fR
76 Markdown file or generated documentation
78 \fB\-\-markdown\-css\fR \fIFILES\fR
79 CSS files to include via <link> in a rendered Markdown file Markdown file or
82 \fB\-\-markdown\-playground\-url\fR \fIURL\fR
85 \fB\-\-markdown\-no\-toc\fR
|
| /third_party/icu/docs/userguide/dev/ |
| D | editing.md | 25 This version of the ICU User Guide is generated directly from the Markdown
27 Markdown files are customized to work with the Jekyll static site generator,
46 from the branch and the Markdown pages root directory (`/docs`).
59 CommonMark Markdown parser, the default Jekyll Markdown parser, Kramdown, is
66 information provided in the header section of the Markdown file according to
71 [Markdown](https://kramdown.gettalong.org/syntax.html) should be preferred over custom
80 Use the markdown notation of [single backtick](https://kramdown.gettalong.org/quickref.html#inline-…
84 Unlike Github-flavored Markdown, in multi-line fenced code
91 following Markdown:
100 following Markdown:
[all …]
|
| /third_party/skia/site/docs/dev/tools/ |
| D | markdown.md | 2 title: 'Markdown'
3 linkTitle: 'Markdown'
10 as Markdown. All other files will be served directly. For example, images can be
11 added and they will be served correctly and referenced from within Markdown
18 https://skia.org/path/to/markdown-file?cl=REITVELD_ISSUE_NUMBER
33 title: 'Markdown'
34 linkTitle: 'Markdown'
38 This is true for both Markdown and HTML pages. See
66 ````markdown
|
| /third_party/skia/m133/site/docs/dev/tools/ |
| D | markdown.md | 2 title: 'Markdown'
3 linkTitle: 'Markdown'
10 as Markdown. All other files will be served directly. For example, images can be
11 added and they will be served correctly and referenced from within Markdown
33 title: 'Markdown'
34 linkTitle: 'Markdown'
38 This is true for both Markdown and HTML pages. See
66 ````markdown
|
| /third_party/rust/rust/tests/run-make/issue-88756-default-output/ |
| D | output-default.stdout | 42 --markdown-css FILES
43 CSS files to include via <link> in a rendered Markdown
47 rendered Markdown file or generated documentation
50 of a rendered Markdown file or generated documentation
53 </body> of a rendered Markdown file or generated
55 --markdown-before-content FILES
57 of a rendered Markdown file or generated documentation
58 --markdown-after-content FILES
60 </body> of a rendered Markdown file or generated
62 --markdown-playground-url URL
[all …]
|
| /third_party/gn/src/gn/ |
| D | standard_out.h | 23 // Convert < and > to < and > when writing markdown output in non-code
32 // If printing markdown, this generates table-of-contents entries with
42 // The link_tag is set, it will be used for markdown output links. This is
43 // used when generating the markdown for all help topics. If empty, no link tag
44 // will be emitted. In non-markdown mode, this parameter will be ignored.
58 // when generating the markdown for all help topics. If empty, no link tag will
59 // be emitted. Used only in markdown mode.
|
| /third_party/skia/third_party/externals/freetype/docs/ |
| D | DOCGUIDE | 118 Markdown Usage
122 support markdown in them. Docwriter uses a markdown parser that
123 follows rules given in John Gruber's markdown guide:
125 https://daringfireball.net/projects/markdown/syntax
128 be referred to as the **FreeType Flavored Markdown**.
134 Markdown headers should not be used directly, because these are added
157 Although unintentional, this is correct markdown behavior.
192 More information on lists in markdown is available at
194 https://daringfireball.net/projects/markdown/syntax#list
216 Markdown syntax for links and images are fully supported.
[all …]
|
| /third_party/rust/rust/src/tools/rust-analyzer/editors/code/ |
| D | rustdoc.markdown.injection.tmGrammar.json | 2 "scopeName": "rustdoc.markdown.injection",
17 "contentName": "meta.embedded.block.markdown",
20 "include": "text.html.markdown"
28 "contentName": "meta.embedded.block.markdown",
31 "include": "text.html.markdown"
|
| /third_party/rust/rust/src/librustdoc/ |
| D | externalfiles.rs | 1 use crate::html::markdown::{ErrorCodes, HeadingOffset, IdMap, Markdown, Playground};
12 /// rendered Markdown file or generated documentation
15 /// a rendered Markdown file or generated documentation
18 /// a rendered Markdown file or generated documentation
42 Markdown { in load()
58 Markdown { in load()
|
| D | markdown.rs | 12 use crate::html::markdown;
13 use crate::html::markdown::{
14 find_testable_code, ErrorCodes, HeadingOffset, IdMap, Markdown, MarkdownWithToc,
62 let playground = playground_url.map(|url| markdown::Playground { crate_name: None, url }); in render()
68 return Err("invalid markdown file: no initial lines starting with `# ` or `%`".to_owned()); in render()
84 Markdown { in render()
137 /// Runs any tests/code examples in the markdown file `input`.
|
| D | lib.rs | 117 mod markdown; module
300 stable("markdown-css", |o| { in opts()
303 "markdown-css", in opts()
304 "CSS files to include via <link> in a rendered Markdown file", in opts()
312 "files to include inline in the <head> section of a rendered Markdown file \ in opts()
322 Markdown file or generated documentation", in opts()
331 Markdown file or generated documentation", in opts()
335 unstable("markdown-before-content", |o| { in opts()
338 "markdown-before-content", in opts()
340 Markdown file or generated documentation", in opts()
[all …]
|
| /third_party/rust/rust/src/doc/rustdoc/src/ |
| D | command-line-arguments.md | 243 ## `--markdown-css`: include more CSS files when rendering markdown
248 $ rustdoc README.md --markdown-css foo.css
251 When rendering Markdown files, this will create a `<link>` element in the
301 ## `--markdown-playground-url`: control the location of the playground
306 $ rustdoc README.md --markdown-playground-url https://play.rust-lang.org/
309 When rendering a Markdown file, this flag gives the base URL of the Rust
313 ## `--markdown-no-toc`: don't generate a table of contents
318 $ rustdoc README.md --markdown-no-toc
321 When generating documentation from a Markdown file, by default, `rustdoc` will
427 Rustdoc only supports Rust source code and Markdown input formats. If the
[all …]
|
| D | what-is-rustdoc.md | 5 takes as an argument either a crate root or a Markdown file, and produces HTML,
122 ## Using standalone Markdown files
124 `rustdoc` can also generate HTML from standalone Markdown files. Let' s
150 Markdown contents.
152 Cargo currently does not understand standalone Markdown files, unfortunately.
|
| D | unstable-features.md | 27 ``````markdown
245 ### `--markdown-before-content`: include rendered Markdown before the content
252 $ rustdoc src/lib.rs -Z unstable-options --markdown-before-content extra.md
253 $ rustdoc README.md -Z unstable-options --markdown-before-content extra.md
259 Markdown renderer before inserting the result into the file.
261 ### `--markdown-after-content`: include rendered Markdown after the content
266 $ rustdoc src/lib.rs -Z unstable-options --markdown-after-content extra.md
267 $ rustdoc README.md -Z unstable-options --markdown-after-content extra.md
273 Markdown renderer before inserting the result into the file.
284 generating `Run` buttons. Unlike `--markdown-playground-url`, this argument works for standalone
[all …]
|
| /third_party/rust/rust/src/librustdoc/passes/ |
| D | mod.rs | 132 /// Attempts to match a range of bytes from parsed markdown to a `Span` in the source code.
139 markdown: &str, in source_span_for_markdown_range()
152 let starting_line = markdown[..md_range.start].matches('\n').count(); in source_span_for_markdown_range()
153 let ending_line = starting_line + markdown[md_range.start..md_range.end].matches('\n').count(); in source_span_for_markdown_range()
158 let md_lines = markdown.split_terminator('\n'); in source_span_for_markdown_range()
160 // The number of bytes from the source span to the markdown span that are not part in source_span_for_markdown_range()
161 // of the markdown, like comment markers. in source_span_for_markdown_range()
187 // Since this is a source line that doesn't include a markdown line, in source_span_for_markdown_range()
|
| /third_party/skia/m133/third_party/externals/libwebp/doc/ |
| D | template.html | 63 #markdown-toc ul {
66 ul#markdown-toc {
71 ul#markdown-toc ul {
74 ul#markdown-toc ul ul{
77 ul#markdown-toc + hr {
|
| /third_party/skia/third_party/externals/libwebp/doc/ |
| D | template.html | 63 #markdown-toc ul {
66 ul#markdown-toc {
71 ul#markdown-toc ul {
74 ul#markdown-toc ul ul{
77 ul#markdown-toc + hr {
|
| /third_party/curl/docs/ |
| D | CURLDOWN.md | 9 A markdown-like syntax for libcurl man pages.
23 Take advantage of the fact that people these days are accustomed to markdown
24 by using a markdown-like syntax.
39 Since curldown looks similar to markdown, we use `.md` extensions on the
107 Following the header in the file, is the manual page using markdown-like
147 To make sure curldown documents render correctly as markdown, all literal
|
| /third_party/rust/rust/src/tools/rustfmt/tests/target/issue-5238/ |
| D | markdown_header_wrap_comments_false.rs | 3 /// no markdown header so rustfmt should wrap this comment when `format_code_in_doc_comments = true…
8 /// # We're using a markdown header here so rustfmt should refuse to wrap this comment in all circu…
10 …// # We're using a markdown header in an inline comment. rustfmt should be able to wrap this comme… in documented_with_markdown_header()
|
| D | markdown_header_wrap_comments_true.rs | 3 /// no markdown header so rustfmt should wrap this comment when
10 /// # We're using a markdown header here so rustfmt should refuse to wrap this comment in all circu…
12 // # We're using a markdown header in an inline comment. rustfmt should be in documented_with_markdown_header()
|
| /third_party/rust/rust/src/tools/rustfmt/tests/source/issue-5238/ |
| D | markdown_header_wrap_comments_false.rs | 3 /// no markdown header so rustfmt should wrap this comment when `format_code_in_doc_comments = true…
8 /// # We're using a markdown header here so rustfmt should refuse to wrap this comment in all circu…
10 …// # We're using a markdown header in an inline comment. rustfmt should be able to wrap this comme… in documented_with_markdown_header()
|
| D | markdown_header_wrap_comments_true.rs | 3 /// no markdown header so rustfmt should wrap this comment when `format_code_in_doc_comments = true…
8 /// # We're using a markdown header here so rustfmt should refuse to wrap this comment in all circu…
10 …// # We're using a markdown header in an inline comment. rustfmt should be able to wrap this comme… in documented_with_markdown_header()
|
| /third_party/rust/rust/compiler/rustc_errors/src/markdown/ |
| D | mod.rs | 1 //! A simple markdown parser that can write formatted text to the terminal
10 /// An AST representation of a Markdown document
15 /// Parse a markdown string to a tokenstream
32 /// A single tokentree within a Markdown document
|
| /third_party/jerryscript/tools/ |
| D | gen-doctest.py | 29 An extractor to process Markdown files and find doctests inside.
109 Find doctests in a Markdown file and process them according to the
156 parser = argparse.ArgumentParser(description='Markdown doctest extractor', epilog="""
157 The tool extracts specially marked fenced C code blocks from the input Markdown files
159 but valid Markdown links/comments that must be added before the fenced code blocks:
171 help='input Markdown file(s)')
|
| /third_party/skia/m133/relnotes/ |
| D | README.md | 5 All Markdown (`*.md`) files in this directory are treated as release notes -
13 ## Markdown Support
15 Notes are free to use nearly all of the Markdown language. However, because they
|