Regenerate derived doc formats.

Author: Enyium

src/doc/man/generated_txt/cargo-add.txt

@@ -1,20 +1,20 @@
 CARGO-ADD(1)
 
 NAME
-       cargo-add - Add dependencies to a Cargo.toml manifest file
+       cargo-add — Add dependencies to a Cargo.toml manifest file
 
 SYNOPSIS
-       cargo add [options] crate...
+       cargo add [options] crate…
        cargo add [options] --path path
-       cargo add [options] --git url [crate...]
+       cargo add [options] --git url [crate…]
 
 DESCRIPTION
        This command can add or modify dependencies.
 
        The source for the dependency can be specified with:
 
        o  crate@version: Fetch from a registry with a version constraint of
-          "version"
+          “version”
 
        o  --path path: Fetch from the specified path
 
@@ -34,7 +34,7 @@ DESCRIPTION
 
        Upon successful invocation, the enabled (+) and disabled (-) features
        <https://doc.rust-lang.org/cargo/reference/features.md> of the specified
-       dependency will be listed in the command's output.
+       dependency will be listed in the command’s output.
 
 OPTIONS
    Source options
@@ -80,7 +80,7 @@ OPTIONS
 
    Dependency options
        --dry-run
-           Don't actually write the manifest
+           Don’t actually write the manifest
 
        --rename name
            Rename
@@ -112,10 +112,11 @@ OPTIONS
 
    Display Options
        -v, --verbose
-           Use verbose output. May be specified twice for "very verbose" output
-           which includes extra output such as dependency warnings and build
-           script output. May also be specified with the term.verbose config
-           value <https://doc.rust-lang.org/cargo/reference/config.html>.
+           Use verbose output. May be specified twice for “very verbose”
+           output which includes extra output such as dependency warnings and
+           build script output. May also be specified with the term.verbose
+           config value
+           <https://doc.rust-lang.org/cargo/reference/config.html>.
 
        -q, --quiet
            Do not print cargo log messages. May also be specified with the

src/doc/man/generated_txt/cargo-bench.txt

@@ -1,7 +1,7 @@
 CARGO-BENCH(1)
 
 NAME
-       cargo-bench - Execute benchmarks of a package
+       cargo-bench — Execute benchmarks of a package
 
 SYNOPSIS
        cargo bench [options] [benchname] [-- bench-options]
@@ -11,11 +11,11 @@ DESCRIPTION
 
        The benchmark filtering argument benchname and all the arguments
        following the two dashes (--) are passed to the benchmark binaries and
-       thus to libtest (rustc's built in unit-test and micro-benchmarking
+       thus to libtest (rustc’s built in unit-test and micro-benchmarking
        framework). If you are passing arguments to both Cargo and the binary,
        the ones after -- go to the binary, the ones before go to Cargo. For
-       details about libtest's arguments see the output of cargo bench --
-       --help and check out the rustc book's chapter on how tests work at
+       details about libtest’s arguments see the output of cargo bench --
+       --help and check out the rustc book’s chapter on how tests work at
        <https://doc.rust-lang.org/rustc/tests/index.html>.
 
        As an example, this will run only the benchmark named foo (and skip
@@ -52,7 +52,7 @@ DESCRIPTION
 OPTIONS
    Benchmark Options
        --no-run
-           Compile, but don't run benchmarks.
+           Compile, but don’t run benchmarks.
 
        --no-fail-fast
            Run all benchmarks regardless of failure. Without this flag, Cargo
@@ -74,7 +74,7 @@ OPTIONS
        passing --workspace), and a non-virtual workspace will include only the
        root crate itself.
 
-       -p spec..., --package spec...
+       -p spec…, --package spec…
            Benchmark only the specified packages. See cargo-pkgid(1) for the
            SPEC format. This flag may be specified multiple times and supports
            common Unix glob patterns like *, ? and []. However, to avoid your
@@ -88,7 +88,7 @@ OPTIONS
        --all
            Deprecated alias for --workspace.
 
-       --exclude SPEC...
+       --exclude SPEC…
            Exclude the specified packages. Must be used in conjunction with the
            --workspace flag. This flag may be specified multiple times and
            supports common Unix glob patterns like *, ? and []. However, to
@@ -136,23 +136,23 @@ OPTIONS
        use single quotes or double quotes around each glob pattern.
 
        --lib
-           Benchmark the package's library.
+           Benchmark the package’s library.
 
-       --bin name...
+       --bin name…
            Benchmark the specified binary. This flag may be specified multiple
            times and supports common Unix glob patterns.
 
        --bins
            Benchmark all binary targets.
 
-       --example name...
+       --example name…
            Benchmark the specified example. This flag may be specified multiple
            times and supports common Unix glob patterns.
 
        --examples
            Benchmark all example targets.
 
-       --test name...
+       --test name…
            Benchmark the specified integration test. This flag may be specified
            multiple times and supports common Unix glob patterns.
 
@@ -165,7 +165,7 @@ OPTIONS
            integration tests, etc.). Targets may be enabled or disabled by
            setting the test flag in the manifest settings for the target.
 
-       --bench name...
+       --bench name…
            Benchmark the specified benchmark. This flag may be specified
            multiple times and supports common Unix glob patterns.
 
@@ -227,7 +227,7 @@ OPTIONS
 
        --ignore-rust-version
            Benchmark the target even if the selected Rust compiler is older
-           than the required Rust version as configured in the project's
+           than the required Rust version as configured in the project’s
            rust-version field.
 
        --timings=fmts
@@ -265,10 +265,11 @@ OPTIONS
            cargo bench -- --nocapture
 
        -v, --verbose
-           Use verbose output. May be specified twice for "very verbose" output
-           which includes extra output such as dependency warnings and build
-           script output. May also be specified with the term.verbose config
-           value <https://doc.rust-lang.org/cargo/reference/config.html>.
+           Use verbose output. May be specified twice for “very verbose”
+           output which includes extra output such as dependency warnings and
+           build script output. May also be specified with the term.verbose
+           config value
+           <https://doc.rust-lang.org/cargo/reference/config.html>.
 
        -q, --quiet
            Do not print cargo log messages. May also be specified with the
@@ -303,18 +304,19 @@ OPTIONS
               for more details. Conflicts with human and short.
 
            o  json-diagnostic-short: Ensure the rendered field of JSON messages
-              contains the "short" rendering from rustc. Cannot be used with
-              human or short.
+              contains the “short” rendering from rustc. Cannot be used
+              with human or short.
 
            o  json-diagnostic-rendered-ansi: Ensure the rendered field of JSON
               messages contains embedded ANSI color codes for respecting
-              rustc's default color scheme. Cannot be used with human or short.
+              rustc’s default color scheme. Cannot be used with human or
+              short.
 
            o  json-render-diagnostics: Instruct Cargo to not include rustc
               diagnostics in JSON messages printed, but instead Cargo itself
-              should render the JSON diagnostics coming from rustc. Cargo's own
-              JSON diagnostics and others coming from rustc are still emitted.
-              Cannot be used with human or short.
+              should render the JSON diagnostics coming from rustc. Cargo’s
+              own JSON diagnostics and others coming from rustc are still
+              emitted. Cannot be used with human or short.
 
    Manifest Options
        --manifest-path path

src/doc/man/generated_txt/cargo-build.txt

@@ -1,7 +1,7 @@
 CARGO-BUILD(1)
 
 NAME
-       cargo-build - Compile the current package
+       cargo-build — Compile the current package
 
 SYNOPSIS
        cargo build [options]
@@ -24,7 +24,7 @@ OPTIONS
        passing --workspace), and a non-virtual workspace will include only the
        root crate itself.
 
-       -p spec..., --package spec...
+       -p spec…, --package spec…
            Build only the specified packages. See cargo-pkgid(1) for the SPEC
            format. This flag may be specified multiple times and supports
            common Unix glob patterns like *, ? and []. However, to avoid your
@@ -38,7 +38,7 @@ OPTIONS
        --all
            Deprecated alias for --workspace.
 
-       --exclude SPEC...
+       --exclude SPEC…
            Exclude the specified packages. Must be used in conjunction with the
            --workspace flag. This flag may be specified multiple times and
            supports common Unix glob patterns like *, ? and []. However, to
@@ -68,23 +68,23 @@ OPTIONS
        use single quotes or double quotes around each glob pattern.
 
        --lib
-           Build the package's library.
+           Build the package’s library.
 
-       --bin name...
+       --bin name…
            Build the specified binary. This flag may be specified multiple
            times and supports common Unix glob patterns.
 
        --bins
            Build all binary targets.
 
-       --example name...
+       --example name…
            Build the specified example. This flag may be specified multiple
            times and supports common Unix glob patterns.
 
        --examples
            Build all example targets.
 
-       --test name...
+       --test name…
            Build the specified integration test. This flag may be specified
            multiple times and supports common Unix glob patterns.
 
@@ -97,7 +97,7 @@ OPTIONS
            integration tests, etc.). Targets may be enabled or disabled by
            setting the test flag in the manifest settings for the target.
 
-       --bench name...
+       --bench name…
            Build the specified benchmark. This flag may be specified multiple
            times and supports common Unix glob patterns.
 
@@ -163,7 +163,7 @@ OPTIONS
 
        --ignore-rust-version
            Build the target even if the selected Rust compiler is older than
-           the required Rust version as configured in the project's
+           the required Rust version as configured in the project’s
            rust-version field.
 
        --timings=fmts
@@ -204,10 +204,11 @@ OPTIONS
 
    Display Options
        -v, --verbose
-           Use verbose output. May be specified twice for "very verbose" output
-           which includes extra output such as dependency warnings and build
-           script output. May also be specified with the term.verbose config
-           value <https://doc.rust-lang.org/cargo/reference/config.html>.
+           Use verbose output. May be specified twice for “very verbose”
+           output which includes extra output such as dependency warnings and
+           build script output. May also be specified with the term.verbose
+           config value
+           <https://doc.rust-lang.org/cargo/reference/config.html>.
 
        -q, --quiet
            Do not print cargo log messages. May also be specified with the
@@ -242,18 +243,19 @@ OPTIONS
               for more details. Conflicts with human and short.
 
            o  json-diagnostic-short: Ensure the rendered field of JSON messages
-              contains the "short" rendering from rustc. Cannot be used with
-              human or short.
+              contains the “short” rendering from rustc. Cannot be used
+              with human or short.
 
            o  json-diagnostic-rendered-ansi: Ensure the rendered field of JSON
               messages contains embedded ANSI color codes for respecting
-              rustc's default color scheme. Cannot be used with human or short.
+              rustc’s default color scheme. Cannot be used with human or
+              short.
 
            o  json-render-diagnostics: Instruct Cargo to not include rustc
               diagnostics in JSON messages printed, but instead Cargo itself
-              should render the JSON diagnostics coming from rustc. Cargo's own
-              JSON diagnostics and others coming from rustc are still emitted.
-              Cannot be used with human or short.
+              should render the JSON diagnostics coming from rustc. Cargo’s
+              own JSON diagnostics and others coming from rustc are still
+              emitted. Cannot be used with human or short.
 
        --build-plan
            Outputs a series of JSON messages to stdout that indicate the